[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-6ce51c431019310ca03371355a4366c4649fa349@git.kernel.org>
Date: Thu, 23 Apr 2009 06:48:31 GMT
From: tip-bot for Luis Henriques <henrix@...o.pt>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
henrix@...o.pt, sfr@...b.auug.org.au, tglx@...utronix.de,
mingo@...e.hu
Subject: [tip:irq/genirq] genirq: do not execute DEBUG_SHIRQ when irq setup failed
Commit-ID: 6ce51c431019310ca03371355a4366c4649fa349
Gitweb: http://git.kernel.org/tip/6ce51c431019310ca03371355a4366c4649fa349
Author: Luis Henriques <henrix@...o.pt>
AuthorDate: Wed, 1 Apr 2009 18:06:35 +0100
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Thu, 23 Apr 2009 08:45:48 +0200
genirq: do not execute DEBUG_SHIRQ when irq setup failed
When requesting an IRQ, the DEBUG_SHIRQ code executes a fake IRQ just to make
sure the driver is ready to receive an IRQ immediately. The problem was that
this fake IRQ was being executed even if interrupt line failed to be allocated
by __setup_irq.
Signed-off-by: Luis Henriques <henrix@...o.pt>
LKML-Reference: <20090401170635.GA4392@...es.domain.com>
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
[ fixed bug pointed out by a warning reported by Stephen Rothwell ]
Cc: Stephen Rothwell <sfr@...b.auug.org.au>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
kernel/irq/manage.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 1516ab7..8c68d5b 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -768,7 +768,7 @@ int request_irq(unsigned int irq, irq_handler_t handler,
kfree(action);
#ifdef CONFIG_DEBUG_SHIRQ
- if (irqflags & IRQF_SHARED) {
+ if (!retval && (irqflags & IRQF_SHARED)) {
/*
* It's a shared IRQ -- the driver ought to be prepared for it
* to happen immediately, so let's make sure....
--
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