On 18/07/2018 00:54:21+0300, Andy Shevchenko wrote: > On Wed, Jul 18, 2018 at 12:42 AM, Alexandre Belloni > <alexandre.belloni@xxxxxxxxxxx> wrote: > > On 18/07/2018 00:30:49+0300, Andy Shevchenko wrote: > >> On Wed, Jul 18, 2018 at 12:30 AM, Andy Shevchenko > >> <andy.shevchenko@xxxxxxxxx> wrote: > >> > On Tue, Jul 17, 2018 at 5:23 PM, Alexandre Belloni > >> > <alexandre.belloni@xxxxxxxxxxx> wrote: > >> > >> > Reviewed-by: Andy Shevchenko <andy.shevchenko@xxxxxxxxx> > >> > > >> >> Signed-off-by: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx> > >> > >> Shouldn't it have a Fixes tag? > >> > > > > Well, I'm not sure how far this can be backported. It also seems nobody > > ever hit that while our hardware will hit it at every boot. > > > > I'll try to find out. > > No-one enabled CONFIG_DEBUG_SHIRQ? > Nope, this is a real HW IRQ. I meant find out up to when it can be sanely backported. -- Alexandre Belloni, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com -- 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
