From: Rob Herring <firstname.lastname@example.org> To: Thorsten Leemhuis <email@example.com> Cc: Charles Keepax <firstname.lastname@example.org>, Peter Chen <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org>, Linux USB List <email@example.com>, "firstname.lastname@example.org" <email@example.com>, "firstname.lastname@example.org" <email@example.com> Subject: Re: ChipIdea USB regression Date: Tue, 18 Jan 2022 12:37:24 -0600 [thread overview] Message-ID: <CAL_JsqLQnPc=eSz_OD4HaK-MqXmmnfQkRNbHHLXpRH--w=dBNQ@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Tue, Jan 18, 2022 at 11:34 AM Thorsten Leemhuis <email@example.com> wrote: > > On 18.01.22 17:53, Rob Herring wrote: > > On Sun, Jan 16, 2022 at 4:21 AM Thorsten Leemhuis > > <firstname.lastname@example.org> 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@ediswmail.ad.cirrus.com/ 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 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  https://gitlab.com/robherring/pw-utils
prev parent reply other threads:[~2022-01-18 18:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 10:56 Charles Keepax 2022-01-14 11:18 ` Charles Keepax 2022-01-15 15:55 ` Rob Herring 2022-01-17 9:26 ` Charles Keepax 2022-01-17 9:55 ` Charles Keepax 2022-01-18 14:39 ` Rob Herring 2022-01-18 16:16 ` Charles Keepax 2022-01-16 10:21 ` Thorsten Leemhuis 2022-01-18 16:53 ` Rob Herring 2022-01-18 17:33 ` Thorsten Leemhuis 2022-01-18 18:37 ` Rob Herring [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAL_JsqLQnPc=eSz_OD4HaK-MqXmmnfQkRNbHHLXpRH--w=dBNQ@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: ChipIdea USB regression' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).