On Mon, Feb 21, 2022 at 09:52:34AM +0000, Lee Jones wrote: > On Thu, 17 Feb 2022, Lee Jones wrote: > > > On Thu, 17 Feb 2022, Greg KH wrote: > > > > > On Thu, Feb 17, 2022 at 03:57:23PM +0000, Lee Jones wrote: > > > > Good afternoon Daniel, > > > > > > > > On Mon, 22 Nov 2021, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > > > > > > > The patch below does not apply to the 5.4-stable tree. > > > > > If someone wants it applied there, or to any other stable or longterm > > > > > tree, then please email the backport, including the original git commit > > > > > id to <stable@xxxxxxxxxxxxxxx>. > > > > > > > > We are in receipt of a bug report which cites this patch as the fix. > > > > > > Does the bug report really say that this issue is present in the 5.4 > > > kernel tree? Anything older? > > > > Not specifically, but the commit referenced in the Fixes tag landed in > > v5.5. and was successfully back-ported to v5.4.144. > > Another potential avenue might to be revert the back-ported commit > which caused the issue from v5.4.y. Unless that was fixing a different issue? I have no idea at this point what commit you are talking about, sorry :( greg k-h
