On Thu, 2020-05-07 at 14:23 +0100, Pete Batard wrote: [...] > I specifically designed the patch I submitted for easy review and > integration, because there are missing elements from 4.x that are > present in 5.x, that we have to compensate for. I would rather not have > to split it, especially as I believe it should be included as a matter > of priority and we're simply adding delays.
I personally find it much easier to review backports in this form, and it is the usual practice in Debian to backport changes in this form where possible. > If Debian 11 was planning to continue to use a 4.x kernel, I could see > some point in splitting the patch and ensuring, so that it *might* be > easier to maintain for many years to come. But, from what I gather, > Debian 11 will bump kernel major, so any work being done making the 4.x > backport (which is not that complex, sorry, especially as I made sure to > already group the code changes in a manner that makes it easier to > handle) easier to maintain in the long run seems like a waste of time, > even if 10.x may see long time support for a few more years... [...] Debian 10 will be supported for 4 more years, in fact. During that time this driver may well see other changes backported through the stable process. Based on past experience, I think it will be easier to resolve any conflicts if our patches make smaller changes. So please don't assume what's "easier to handle" for us. Ben. -- Ben Hutchings - Debian developer, member of kernel, installer and LTS teams
signature.asc
Description: This is a digitally signed message part
