Re: random.c backports for 5.18, 5.17, 5.15, and prior

["Jason A. Donenfeld" <Jason@zx2c4.com>]

Hey Greg,

On Mon, May 30, 2022 at 10:11:52AM +0200, Greg KH wrote:
> For 5.4 I just don't think it's worth the trouble.  Devices based on
> that old kernel aren't going to want to deal with the churn like this,
> and being forced to add the WG code to it also seems like a lot of
> unnecessary work for everyone (including yourself.)
> 
> But, I do know that a lot of Android devices are still relying on 5.4,
> they already have WG in their kernels so overall this might be a smaller
> diff for them?
> 
> I don't really know, do you have any people/companies/devices using 5.4
> that would want this all added that you can show it is worth it for?

I think if it's in 5.10, it makes sense to at least try to get it into
5.4 and below for the same reasons. I'm traveling over the next week or
so, but I think I'll attempt to do a straight backport of it (sans-wg)
like I did for 5.10. As mentioned, it's harder, but that doesn't mean
it's impossible. I might give up in exasperation or perhaps find it too
onerous. But hopefully I'll be able to reuse the work I did for the
Android wg backports. Anyway, no guarantees -- it's not a trivial walk
in the park -- but I'll give it a shot and let you know if I can make it
work.

Jason