[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200310184921.23552-1-maz@kernel.org>
Date: Tue, 10 Mar 2020 18:49:17 +0000
From: Marc Zyngier <maz@...nel.org>
To: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc: Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Russell King <linux@....linux.org.uk>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Ludovic Desroches <ludovic.desroches@...rochip.com>,
Zenghui Yu <yuzenghui@...wei.com>
Subject: [PATCH 0/4] irqchip: Random irq_retrigger fixes
As I was investigating some ugly retrigger locking issues (see patch 4),
I managed to find three occurences of irq_retrigger callbacks that return
the wrong value, leading to a SW retrigger on top of the HW one.
Not really a big deal, but definitely worth fixing.
Marc Zyngier (4):
irqchip/atmel-aic: Fix irq_retrigger callback return value
irqchip/atmel-aic5: Fix irq_retrigger callback return value
ARM: sa1111: Fix irq_retrigger callback return value
irqchip/gic-v4: Provide irq_retrigger to avoid circular locking
dependency
arch/arm/common/sa1111.c | 7 +++++--
drivers/irqchip/irq-atmel-aic.c | 2 +-
drivers/irqchip/irq-atmel-aic5.c | 2 +-
drivers/irqchip/irq-gic-v3-its.c | 6 ++++++
4 files changed, 13 insertions(+), 4 deletions(-)
--
2.20.1
Powered by blists - more mailing lists