* Linus Walleij <linus.walleij@xxxxxxxxxx> [150506 06:22]: > On Fri, Apr 24, 2015 at 1:54 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > At some point with all the GPIO clean-up we've broken the > > MPUIO interrupts. Those are just a little bit different from > > the GPIO interrupts, so we can fix it up just by setting > > different irqchip functions for it. And then we can just > > remove all old code trying to do the same. > > > > Cc: Aaro Koskinen <aaro.koskinen@xxxxxx> > > Cc: Felipe Balbi <balbi@xxxxxx> > > Cc: Javier Martinez Canillas <javier@xxxxxxxxxxxx> > > Cc: Grygorii Strashko <grygorii.strashko@xxxxxxxxxx> > > Cc: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > > Cc: Nishanth Menon <nm@xxxxxx> > > Cc: Santosh Shilimkar <ssantosh@xxxxxxxxxx> > > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> > > Patch applied for fixes with the ACKs etc, Thanks. Yes this should go in during the -rc cycle as a regresion fix. Sorry I could not exactly pinpoint where we've broken the MPUIO interrupts with all the clean-up. Also the omap1 SPARSE_IRQ changes I recently posted have a dependency to this one so that's another reason to get this one out of the way. No rush with the other ones, those should be OK for v4.2. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
