Message-ID: <2f55b629-2e5b-bd45-e0ea-4e476f603dc8@leemhuis.info>
Date:   Tue, 18 Jan 2022 18:33:47 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Rob Herring <robh@...nel.org>
Cc:     Charles Keepax <ckeepax@...nsource.cirrus.com>,
        Peter Chen <peter.chen@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux USB List <linux-usb@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Re: ChipIdea USB regression

On 18.01.22 17:53, Rob Herring wrote:
> On Sun, Jan 16, 2022 at 4:21 AM Thorsten Leemhuis
> <regressions@...mhuis.info> wrote:
>>
>> [TLDR: I'm adding this regression to regzbot, the Linux kernel
>> regression tracking bot; most text you find below is compiled from a few
>> templates paragraphs some of you might have seen already.]
>>
>> Hi, this is your Linux kernel regression tracker speaking.
>>
>> Adding the regression mailing list to the list of recipients, as it
>> should be in the loop for all regressions, as explained here:
>> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
>>
>> On 14.01.22 11:56, Charles Keepax wrote:
>>> Hi guys,
>>>
>>> My Zynq based board stopped booting today, a bisect points to this
>>> patch:
>>>
>>> commit 0f153a1b8193 ("usb: chipidea: Set the DT node on the child device")
>>
>> Thanks for the report.
>>
>> To be sure this issue doesn't fall through the cracks unnoticed, I'm
>> adding it to regzbot, my Linux kernel regression tracking bot:
>>
>> #regzbot ^introduced 0f153a1b8193
>> #regzbot title usb: chipidea: Zynq based board stopped booting today
>> #regzbot ignore-activity
>>
>> Reminder: when fixing the issue, please add a 'Link:' tag with the URL
>> to the report (the parent of this mail) using the kernel.org redirector,
> 
> 'kernel.org redirector' is lore.kernel.org? It would be clearer to
> just say that.

Yes/No it's lore.kernel.org/r/ (and not lore.kernel.org/list-foo/).
You're right I'll rephrase next time.

>> as explained in 'Documentation/process/submitting-patches.rst'. Regzbot
>> then will automatically mark the regression as resolved once the fix
>> lands in the appropriate tree. For more details about regzbot see footer.
> 
> Would it be possible for you to provide the exact link tag in your
> reports? That would be easier and less error prone than describing
> what to do in prose.

Hmm. The webui already provides this (and other things you likely want
to add) when you show the details for a tracked regression or visit its
individual page:

https://linux-regtracking.leemhuis.info/regzbot/mainline/
https://linux-regtracking.leemhuis.info/regzbot/regression/20220114105620.GK18506@ediswmail.ad.cirrus.com/

I see that it would be convenient for developers and less error prone if
I could mention the proper Link: tag in mails like the one you quoted,
that's why I considered that already. But it would make the regression
tracker's job (aka my "job", which I'm kinda doing in my spare time) yet
again somewhat harder, as I see no easy solution to automate that when
writing these mails (which I do with thunderbird, currently). That's why
I decided to not do that for now, as that job is already hard enough and
I don't want to get burned out by this a second time; and those link
tags are something that were expected from developers even before I came
with regzbot.

But well, maybe over time I can up with some idea to make this easy for
me, then I'll gladly provide that service. One easy way to make this
happen would be: regzbot could send a confirmation mail when it adds a
regression to the list of tracked issues and mention the Link: tag
there. But that would be yet another mail in all out inboxes. But maybe
such a mail would be good for other reasons, too.

Ciao, Thorsten

Powered by blists - more mailing lists