[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1260350401-9858-1-git-send-email-u.kleine-koenig@pengutronix.de>
Date: Wed, 9 Dec 2009 10:20:01 +0100
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: x86@...nel.org
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: [PATCH] irq: handle irq0 special only on x86
I just noticed this when digging in the irq handling. At least for arm
this doesn't make sense. Not sure if x86 is the only arch this test
is valid for, but probably it is.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...hat.com>
Cc: H. Peter Anvin <hpa@...or.com>
---
kernel/irq/spurious.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/irq/spurious.c b/kernel/irq/spurious.c
index 22b0a6e..4996b66 100644
--- a/kernel/irq/spurious.c
+++ b/kernel/irq/spurious.c
@@ -199,8 +199,10 @@ try_misrouted_irq(unsigned int irq, struct irq_desc *desc,
if (irqfixup < 2)
return 0;
+#if defined(CONFIG_ARCH_X86)
if (!irq)
return 1;
+#endif
/*
* Since we don't get the descriptor lock, "action" can
--
1.6.5.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists