summaryrefslogtreecommitdiffstats
path: root/kernel/irq
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2009-05-01 15:16:04 +0200
committerThomas Gleixner <tglx@linutronix.de>2009-05-01 15:16:04 +0200
commitd7226fb6ec5d4f325e4e7fd905894e2ea3eb3ae0 (patch)
treeaa5601ffd1103f5ba8662722a0c88cfe1990a301 /kernel/irq
parentLinux 2.6.30-rc4 (diff)
downloadlinux-d7226fb6ec5d4f325e4e7fd905894e2ea3eb3ae0.tar.xz
linux-d7226fb6ec5d4f325e4e7fd905894e2ea3eb3ae0.zip
Revert "genirq: assert that irq handlers are indeed running in hardirq context"
This reverts commit 044d408409cc4e1bc75c886e27ca85c270db104c. The commit added a warning when handle_IRQ_event() is called outside of hard interrupt context. This breaks the generic tasklet based interrupt resend mechanism which is used when the hardware has no way to retrigger the interrupt. So we get a warning for a use case which is correct and worked for years. Remove it. Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'kernel/irq')
-rw-r--r--kernel/irq/handle.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
index d82142be8dd2..26e08754744f 100644
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@ -363,8 +363,6 @@ irqreturn_t handle_IRQ_event(unsigned int irq, struct irqaction *action)
irqreturn_t ret, retval = IRQ_NONE;
unsigned int status = 0;
- WARN_ONCE(!in_irq(), "BUG: IRQ handler called from non-hardirq context!");
-
if (!(action->flags & IRQF_DISABLED))
local_irq_enable_in_hardirq();