Re: backport of patches 8238b4579866b7c1bb99883cfe102a43db5506ff and d6ffe6067a54972564552ea45d320fb98db1ac5e

[Greg KH <gregkh@linuxfoundation.org>]

On Tue, Oct 11, 2022 at 05:48:26AM -0400, Mikulas Patocka wrote:
> 
> 
> On Mon, 10 Oct 2022, Greg KH wrote:
> 
> > Nope, these cause loads of breakages.  See
> > https://lore.kernel.org/r/09eca44e-4d91-a060-d48c-d0aa41ac5045@roeck-us.net
> > for one such example, and I know kbuild sent you other build problems.
> > I'll drop all of these from the stable trees now.  Please feel free to
> > resend them when you have the build issues worked out.
> > 
> > thanks,
> > 
> > greg k-h
> 
> I don't have cross compilers for all the architectures that Linux 
> supports. Is there some way how to have the patch compile-tested before I 
> send it to you?

You can download those compilers from kernel.org, they are all available
there.

> Or - would you accept this patch instead of the upstream patch? It fixes 
> the same bug as the upstream patch, but it's noticeably smaller and it 
> could be applied to the stable kernels 4.19 to 5.19.

We should stick with what is in Linus's tree so as to not cause new
bugs, and to make future backports easier.

thanks,

greg k-h