On Wednesday, 29 June 2022 15:24:45 CEST Ben Hutchings wrote: > Control: tag -1 patch > Control: tag -1 - help > > On Wed, 2022-06-22 at 11:47 +0200, Diederik de Haas wrote: > > On Tuesday, 21 June 2022 16:11:42 CEST Diederik de Haas wrote: > > > > So yes, this needs to also be fixed upstream (hence me including that > > > > tag when reporbugging), but perhaps Debian can quickfix. > > > > > > What I have observed so far is that a commit needs to be accepted > > > upstream > > > (but doesn't have to have gone through the whole 'chain of command') > > > before a temporary patch is accepted to quickly fix it in Debian. > > > > I made an initial attempt at a patch, see attachment. > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html# > > s4.2.2 describes a way to test whether this patch fixes the issue. > > (Just in case. I'm reasonably sure you already know this) > > Looks good to me. Can you send it on to stable@vger.kernel.org? > You'll need to add your Signed-off-by. I proposed my patch to expedite things and (much) prefer that Thorsten would send it (that's why I explicitly omitted the Signed-off-by statement). If there are follow up questions, they would also be directed to the person who found the issue and is the right person to answer them. I'd have to relay them and possibly introduce noise in the communication. I can do it, but I would like Thorsten to test the patch and confirm it actually does fix it. Having a Tested-By tag would be nice. When submitting a MR to the Debian kernel, I'm rightfully expected to have verified it does what it is supposed to do. For the upstream kernel, I'd expect the same at a minimum. Is the prefix I used for the patch, the correct one?
Attachment:
signature.asc
Description: This is a digitally signed message part.