On Tue, 26 Mar 2013, Greg KH wrote: > On Tue, Mar 26, 2013 at 09:37:53PM +0100, Thomas Gleixner wrote: > > On Thu, 21 Mar 2013, Greg KH wrote: > > > > > On Thu, Mar 21, 2013 at 06:12:02PM +0100, Gerlando Falauto wrote: > > > > This patchset addresses a regression found with the Orion GPIO controller > > > > when both Edge- and Level- based interrupts are requested within the same > > > > GPIO chip. The regression was introduced by e59347a > > > > "arm: orion: Use generic irq chip" > > > > > > > > thereby affecting all kernel releases since 3.0.x. > > > > > > <formletter> > > > > > > This is not the correct way to submit patches for inclusion in the > > > stable kernel tree. Please read Documentation/stable_kernel_rules.txt > > > for how to do this properly. > > > > > > </formletter> > > > > Aside of that it would be less intrusive for the stable series to > > revert the offending commit(s), if that is possible. > > If it is reverted in Linus's tree, yes, I can do that. But if so, > please just tag that revert with the Cc: stable marking and then I can > pick it up properly. > > Otherwise, no, I can't revert something that isn't already fixed in > upstream first. I know. The proper thing would be: patch 1/n revert (cc'ed to stable) patch 2-m/n fix infrastructure patch n/n redo the commit with the proper change Though I don't know if it's possible. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html