> > That makes sense. Porting to 4.19 means, using 4.19 as the base for this > > patch and then send out. So, the patch will appear in the next release > > after 4.19 earliest. > > My understanding of this is that > the 9a9e295e7c5c0409c020088b0ae017e6c2b7df6e patch > was written for 4.19 and sent for inclusion in mainline, but not added > before v4.20-rc1. Not quite, please read again: v4.19 was the *base*. The patch was put *on top* of it. It can't be *for* v4.19 because v4.19 was already released. > If you can send your 4.14 patch for inclusion in 4.14, and ask for > 9a9e295e7c5c0409c020088b0ae017e6c2b7df6e to be merged to 4.19 I think we > are all good here. This goes to Jonas, I had nothing to do with this patch other than applying the version which was sent to me. I agree though, that it would be nice if Jonas could send this patch for 4.14, so it could be send further to stable kernels. Regards, Wolfram
Attachment:
signature.asc
Description: PGP signature
