On Tue, Mar 13, 2012 at 01:48:07PM -0700, David Miller wrote: > From: Simon Kirby <[email protected]> > Date: Tue, 13 Mar 2012 10:22:30 -0700 > > > Please cherry-pick 4648dc97af9d496218a05353b0e442b3dfa6aaab into 3.2.11. > > This has been broken since 3.2.9 with the inclusion of > > daef52bab1fd26e24e8e9578f8fb33ba1d0cb412, which a lot of people seem to > > be hitting. > > I'll submit this when I next submit a round of networking fixes to > -stable. > > Please don't request special networking -stable fixes to be applied > out-of-band like this. I'll take care of things when the time is > right and this patch is already queued up into my -stable queue which > is published on patchwork for everyone to see.
Ok, make sense. So, is the easiest way for me to find this out to look at the upstream commit with gitk, note the merge came from you, and assume this is how the stable path should be? Greg's patches are flat commits, so I can't see that you pushed 85a90ef604578b9825d3b7e9d1e3a103357bb668 to him, only that the upstream commit went into Linus (for the current release) that way. Just trying to understand the mechanics. Thanks :) Simon- -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
