From: Thorsten Leemhuis <email@example.com> To: Greg KH <firstname.lastname@example.org> Cc: Linus Torvalds <email@example.com>, Linux Kernel Mailing List <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) Date: Mon, 1 Nov 2021 17:19:50 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <YYAHaONs8IOdecOs@kroah.com> On 01.11.21 16:27, Greg KH wrote: > On Mon, Nov 01, 2021 at 02:34:21PM +0100, Thorsten Leemhuis wrote: >> On 01.11.21 14:03, Greg KH wrote: >>> 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 firstname.lastname@example.org 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 >>>>>> (email@example.com) 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. >> >> Got it, but I could need some advice on it if you have a minute. >> >> Does that report really look like a regression from your point of view? >> The part "The code has been this way in the kernel for a very long time, >> which suggests that it has been working, [...]" sounds like it is, but >> OTOH it's quite vague. > > Later in the thread it was determined that this is a regression that > showed up in the 3.4 kernel release and the commit id was referenced. Hah, stupid me, sorry, should have looked closer myself, thx for the pointer. >> I'm asking, because with my regression tracking work and regzbot I focus >> on regressions and ignore things that were always broken, as I (at least >> for now) don't want it to become yet another bug tracker (and I guess I >> would quickly drown in bugs as well). > > I agree, this shouldn't be a bug tracker, sorry, I shouldn't have > started this with a report of a really old issue, but it's all I found > at short notice :) No worries, I'm glad I get something to test regzbot better :-D > I've found another report of a regression that is newer for USB and > bounced it to you as well. Hopefully that is a bit easier to track. Many thx, much appreciated! Ciao, Thorsten
prev parent reply other threads:[~2021-11-01 16:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAHk-=wjfbfQobW2jygMvgfJXKmzZNB=UTzBrFs2vTEzVpBXA4Q@mail.gmail.com> 2021-11-01 4:49 ` Thorsten Leemhuis 2021-11-01 11:46 ` Idzibear 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 2021-11-01 13:34 ` Thorsten Leemhuis 2021-11-01 15:27 ` Greg KH 2021-11-01 16:19 ` Thorsten Leemhuis [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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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)' \ /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).