[TLDR: This mail in primarily relevant for Linux regression tracking. A change or fix related to the regression discussed in this thread was posted or applied, but it did not use a Closes: tag to point to the report, as Linus and the documentation call for. Things happen, no worries -- but now the regression tracking bot needs to be told manually about the fix. See link in footer if these mails annoy you.] On 16.09.23 04:21, David Gow wrote: > Le 2023/09/16 à 0:20, Niklas Cassel a écrit : >> On Fri, Sep 15, 2023 at 08:26:58PM +0800, David Gow wrote: >>> In any case, the bisect is done: >>> >>> 624885209f31eb9985bf51abe204ecbffe2fdeea is the first bad commit >>> commit 624885209f31eb9985bf51abe204ecbffe2fdeea >>> Author: Damien Le Moal <dlemoal@xxxxxxxxxx> >>> Date: Thu May 11 03:13:41 2023 +0200 > [...] >> Thank you very much for your effort of bisecting this. >> >> Could you please try this patch and see if it improves things for you: >> https://lore.kernel.org/linux-scsi/20230915022034.678121-1-dlemoal@xxxxxxxxxx/ > > Thanks very much: this seems to fix it here (on top of torvalds/master). #regzbot: introduced: 624885209f31eb9 #regzbot fix: scsi: Do no try to probe for CDL on old drives #regzbot monitor: https://lore.kernel.org/linux-scsi/20230915022034.678121-1-dlemoal@xxxxxxxxxx/ #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.
