On Tue, Jan 18, 2022 at 11:34 AM Thorsten Leemhuis <regressions@xxxxxxxxxxxxx> wrote: > > On 18.01.22 17:53, Rob Herring wrote: > > On Sun, Jan 16, 2022 at 4:21 AM Thorsten Leemhuis > > <regressions@xxxxxxxxxxxxx> 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. Or now lore.kernel.org/all/... > >> 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@xxxxxxxxxxxxxxxxxxxxxxx/ That is the link I was originally expecting for when I went back to this thread. > 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. Fair enough, I thought this was more automated than it is. I have some scripts for writing replies[1] if that helps. I wrote them because I couldn't find any that would quote emails. (Maybe because it's a pain dealing with all the encodings). They are geared toward patches in terms of trimming the email, but shouldn't be too hard to adapt. Rob [1] https://gitlab.com/robherring/pw-utils
