On Fri, Jun 07, 2013 at 03:34:55PM +0800, Li Zefan wrote: > On 2013/6/6 4:05, Greg KH wrote: > > On Tue, Jun 04, 2013 at 03:06:25PM +0800, Li Zefan wrote: > >> Hi Greg, > >> > >> I noticed this patch has been merged into 3.2, 3.5, 3.6 and 3.8, but it > >> was never > >> queued for 3.0 or 3.4. Seems something went wrong, and I actually can > >> trigger > >> this bug in 3.4 stable kernel. > > > > I don't see it merged into the 3.2-stable kernel, what is the git commit > > id of it there? > > > > It's in 3.2.44, and the commit id is ee3c9aabb636fcfc21d53c506362620b55fdd8c6
Nice, I'll try that version, thanks. > > It doesn't apply properly to 3.4 or 3.0, so I can't apply it, > > The strange thing is I can't find the "FAILED: patch ..." email. I don't send those out, if it applies to the most recent stable kernel version, otherwise people would be flooded with them, and almost all of them would be pointless. thanks, greg k-h -- 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
