[TLDR: This mail in primarily relevant for Linux kernel regression tracking that uses a reduced set of recipients. See link in footer if these mails annoy you.] On 02.11.23 16:03, Christian Theune wrote: >> On 2. Nov 2023, at 15:53, Christian Theune <ct@xxxxxxxxxxxxxxx> wrote: >> >> Hi, >> >> I hope i’m not jumping the gun, but I guess I’d be interested in a backport to said issue … ;) > > It appears I jumped the gun. :( > > I guess 6a5b845b57b122534d051129bc4fc85eac7f4a68 mentioned in https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.61 is the fix for this. > > Sorry for the noise and mea culpa. Happens, no worries, but here is a tip that might help avoid this in the future: if you know the mainline commit ids of the culprit and/or the fix, search for them on lore abbreviated to ~8 characters and with a wildcard, as that often will turn up fixes and backports (either in progress or already happened). E.g. https://lore.kernel.org/all/?q=e8368b57* Anyway: #regzbot fix: 6a5b845b57b122534d051129bc4fc85ea #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
