[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <160769813659.482133.5814325145566604439.b4-ty@kernel.org>
Date: Fri, 11 Dec 2020 15:01:41 +0000
From: Marc Zyngier <maz@...nel.org>
To: shawnguo@...nel.org, linux@...musvillemoes.dk, leoyang.li@....com,
mark.rutland@....com, zhiqiang.hou@....com,
Biwen Li <biwen.li@....nxp.com>, robh+dt@...nel.org,
tglx@...utronix.de, linux-kernel@...r.kernel.org,
Valentin Schneider <valentin.schneider@....com>,
linux-arm-kernel@...ts.infradead.org
Cc: xiaobo.xie@....com, Hou Zhiqiang <Zhiqiang.Hou@....com>,
devicetree@...r.kernel.org, Biwen Li <biwen.li@....com>,
jiafei.pan@....com, Florian Fainelli <f.fainelli@...il.com>,
Gregory Clement <gregory.clement@...tlin.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Ray Jui <rjui@...adcom.com>, Andrew Lunn <andrew@...n.ch>,
Scott Branden <sbranden@...adcom.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH 0/5] genirq: Get rid of handle_percpu_devid_fasteoi_ipi()
On Mon, 9 Nov 2020 09:41:16 +0000, Valentin Schneider wrote:
> While hacking on the GIC flow handlers, I grew increasingly suspicious of
> handle_percpu_devid_fasteoi_ipi() and thus did a bit of digging. AFAICT it isn't
> actually needed and handle_percpu_devid_irq() would suffice. Argumentation is in
> patch 1.
>
> Tested on my Juno (GICv2) and eMAG (GICv3).
>
> [...]
Applied to irq/irqchip-next, thanks!
[1/5] irqchip/gic, gic-v3: Make SGIs use handle_percpu_devid_irq()
commit: 6abbd6988971aaa607b026eaa0ffd2301352f2ea
[2/5] irqchip/armada-370-xp: Make IPIs use handle_percpu_devid_irq()
commit: e52e73b7e9f7d08b8c2ef6fb1657105093e22a03
[3/5] irqchip/bcm2836: Make IPIs use handle_percpu_devid_irq()
commit: ffdad793d579c9286c7b67a86d1a3c890fb32082
[4/5] irqchip/hip04: Make IPIs use handle_percpu_devid_irq()
commit: a2e042e13ff322ad523a2f131dd6e03e8bc05053
[5/5] Revert "genirq: Add fasteoi IPI flow"
commit: b388fa50142510fb6477f130bb1b3f05a0a263a1
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists