lib: update DEBUG_SHIRQ docs to match reality

There is no extra interrupt when registering a shared interrupt handler
since 2011. Update the Kconfig text to make it clear and to avoid wrong
assumptions when debugging issues found by it.

Fixes: 6d83f94db95c ("genirq: Disable the SHIRQ_DEBUG call in request_threaded_irq for now")
Link: https://lore.kernel.org/linux-i2c/[email protected]/T/#mf24d7070d7e0c8f17b6be6ceb51df94b7d7613b3
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Acked-by: Andy Shevchenko <[email protected]>
Signed-off-by: Wolfram Sang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 9ad9210d70a135732ad6d12ec320f8f1e13aa131..2bff6315224d9fdb929e01c3739f0c08fabdcb25 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -844,10 +844,10 @@ config DEBUG_SHIRQ
        bool "Debug shared IRQ handlers"
        depends on DEBUG_KERNEL
        help
-         Enable this to generate a spurious interrupt as soon as a shared
-         interrupt handler is registered, and just before one is deregistered.
-         Drivers ought to be able to handle interrupts coming in at those
-         points; some don't and need to be caught.
+         Enable this to generate a spurious interrupt just before a shared
+         interrupt handler is deregistered (generating one when registering
+         is currently disabled). Drivers need to handle this correctly. Some
+         don't and need to be caught.
 
 menu "Debug Oops, Lockups and Hangs"