I posted it to linux-media several weeks ago. Based on email feedback seen in response, it is good to go. There's nothing being waited for that I know about. At this point the timing of where/when it goes is in the V4L maintainer's hands.
-Mike On Wed, 20 Nov 2019, Jan Ceuleers wrote: > On 20/11/2019 17:28, Gary Buhrmaster wrote: > > On Tue, Nov 19, 2019 at 9:59 PM Diego Rivera <[email protected]> > > wrote: > >> Hey! Any news on the patch making it into mainline? And how can I track > >> if/when it's been integrated > >> to the core kernel? > > Just to set some expectations, I think it > > clearly it is not going in to 5.4, and I would > > not be surprised it misses 5.5 (pull requests > > are already being accepted, although as a > > targeted fix, it might get pulled during the > > rc fix cycle), so 5.6 could be the earliest > > for mainline. 5.5 is expected (around) > > March/April 2020, and 5.6 probably around > > June/July 2020. As to when any specific > > distro will repackage the kernel that > > includes the fix, well, that opens up > > another can of bad estimation. > But if Mike tags the fix for stable (and if that tag is accepted) then > it will be backported to stable kernels as well. > _______________________________________________ > pvrusb2 mailing list > [email protected] > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > -- Mike Isely isely @ isely (dot) net PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
