On Tue, Apr 05, 2022 at 10:42:21AM +0100, Maciej W. Rozycki wrote: > On Mon, 4 Apr 2022, Andrew Powers-Holmes wrote: > > > Would the best way to get this merged into 5.10/15 (and maybe .16 just > > for good measure) be to email the stable team (since it's already in > > Linus' tree)? Documentation/process/stable-kernel-rules seems to say > > yes, but I'd like to avoid stepping on anyone's toes given that it's not > > my patch. > > You seem the most severely affected so far, so why not act in your best > interest? I think option #2 applies here and seems quite straightforward > to follow, referring commit 2bc5bab9a763 and using your use case as the > justification. It doesn't have to be the author to request a backport. > > NB I think it has to be backported to all the stable branches made since > the original breakage; i.e. v5.9+ (I haven't kept track of what they are). the fix has a Fixes tag so it will usually ported to stable/longterm kernels. I already saw it in Greg's patch bombs. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
