On Thu, Dec 05, 2013 at 01:41:53AM +0100, Thomas Gleixner wrote: > @all who feel responsible for gic_arch_extn > > On Wed, 4 Dec 2013, Thomas Gleixner wrote: > > I'm going to reply in a separate mail on this, because you have > > brought this to my attention, but you are not responsible in the first > > place for this brainfart. > > Who came up with that gic_arch_extn concept in the first place? If you'd spend more time reviewing IRQ patches then maybe you'd catch this at review time. So please stop your rediculous whinging when most of the problem is your own lack of time. If you must know, it was introduced by TI to work around the power management shortcomings of the architecture mandated GIC. No it doesn't get called for IPIs, but it damned well needs to be called for normal IRQs. At the point it was created, it wasn't clear whether this also applied to local IRQs. Since I *no* *longer* have visibility of what SoC stuff is doing with it, of course it's not going to get fixed when a common pattern emerges. So... congratulations, you've found something which can be improved, which has come to light as the code has evolved and a better understanding of what is required has been discovered. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html