From e87f86497b796ed55fff644bbc75bf1890941829 Mon Sep 17 00:00:00 2001 From: Dmitry Eremin-Solenikov Date: Fri, 21 Nov 2014 13:27:11 +0300 Subject: [PATCH] genirq: handle IRQ 0 in __handle_domain_irq __handle_domain_irq() function will ignore (well, report as bad) the IRQ number 0. On some platforms IRQ0 is bad IRQ. On others it is not. And while platforms are still in the process of converging to not using IRQ number 0 as a valid IRQ, I'd like to propose to use IRQ0 as a valid one in __handle_domain_irq(). Signed-off-by: Dmitry Eremin-Solenikov --- kernel/irq/irqdesc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c index a1782f8..bfbeeb6 100644 --- a/kernel/irq/irqdesc.c +++ b/kernel/irq/irqdesc.c @@ -365,7 +365,7 @@ int __handle_domain_irq(struct irq_domain *domain, unsigned int hwirq, * Some hardware gives randomly wrong interrupts. Rather * than crashing, do something sensible. */ - if (unlikely(!irq || irq >= nr_irqs)) { + if (unlikely(irq >= nr_irqs)) { ack_bad_irq(irq); ret = -EINVAL; } else { -- 2.1.1