From: Greg KH <firstname.lastname@example.org> To: Thorsten Leemhuis <email@example.com> Cc: Linus Torvalds <firstname.lastname@example.org>, Linux Kernel Mailing List <email@example.com>, "firstname.lastname@example.org" <email@example.com> Subject: Re: Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Date: Mon, 1 Nov 2021 14:03:24 +0100 [thread overview] Message-ID: <YX/lnI5gX4TAF5Ea@kroah.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Mon, Nov 01, 2021 at 01:44:01PM +0100, Thorsten Leemhuis wrote: > On 01.11.21 13:33, Greg KH wrote: > > On Mon, Nov 01, 2021 at 05:49:40AM +0100, Thorsten Leemhuis wrote: > >> example by simply forwarding the mail to email@example.com or > >> CCing that address on a reply. I'll handle everything else then and tell > >> regzbot about it. But if you feel adventurous, you can also skip me as > >> the man-in-the-middle and tell the bot directly. To do that, just send a > >> reply to the report to the regressions mailing list > >> (firstname.lastname@example.org) either directly or by CCing it on a reply > >> you would have written anyway; when doing so, place something like > >> '#regzbot ^introduced v5.15..' (separated by blank lines) somewhere in > >> the text, as outlined in regzbot's 'getting started guide' or its > >> reference documentation: > >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md > >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md > >> > >> That's it, regzbot then on its next run will add the report to the list > >> of tracked regression. I'll keep an eye on things and try to fix any > >> problems I notice, as there likely will be a few. But then doesn't need > >> to bother you. > >> > >> There is one thing that would really help: if one or two subsystem > >> maintainers could give regzbot a shot for all the regression reports > >> they get, even for easy fixes, as the bot really needs something to chew > >> on. Any volunteers? > > > > I'll try it for the USB subsystem this merge cycle. > > That will be a great help, many thx. > > > Do you want a bug > > report email redirected to that address or will a simple forward work > > well enough? > > Redirecting will make it a little easier for me, but a simple forward is > fine, too. Ok, I did that now for a USB bug report, hopefully that worked. If not, I can forward it on. thanks, greg k-h
next prev parent reply other threads:[~2021-11-01 13:03 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-31 21:09 Linux 5.15 Linus Torvalds 2021-11-01 0:23 ` Guenter Roeck 2021-11-01 8:13 ` Geert Uytterhoeven 2021-11-02 1:17 ` Guenter Roeck 2021-11-02 1:44 ` Linus Torvalds 2021-11-02 3:19 ` Guenter Roeck 2021-11-01 4:49 ` Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Thorsten Leemhuis [not found] ` <email@example.com> 2021-11-01 11:56 ` Greg KH 2021-11-01 12:54 ` Thorsten Leemhuis 2021-11-01 12:33 ` Greg KH 2021-11-01 12:44 ` Thorsten Leemhuis 2021-11-01 13:03 ` Greg KH [this message] 2021-11-01 13:34 ` Thorsten Leemhuis 2021-11-01 15:27 ` Greg KH 2021-11-01 16:19 ` Thorsten Leemhuis 2021-11-01 15:07 ` Linux 5.15 Andy Shevchenko 2021-11-01 16:19 ` Lee Jones 2021-11-01 17:25 ` Sudip Mukherjee
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=YX/lnI5gX4TAF5Ea@kroah.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15)' \ /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).