From: Thorsten Leemhuis <email@example.com> To: Greg KH <firstname.lastname@example.org> Cc: "email@example.com" <firstname.lastname@example.org> Subject: Re: [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference #forregzbot Date: Wed, 22 Dec 2021 09:37:55 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <YcLGlrW06oddk9SE@kroah.com> On 22.12.21 07:32, Greg KH wrote: > On Tue, Dec 21, 2021 at 07:06:30PM +0100, Thorsten Leemhuis wrote: >> Hi, this is your Linux kernel regression tracker speaking. >> >> For the record: >> >> #regzbot fixed-by: 3f345e907a8e7c56fdebf7231cd67afc85d02aaa >> >> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-linus&id=3f345e907a8e7c56fdebf7231cd67afc85d02aaa >> >> Greg helpfully added a "Link:" tag to make regzbot happy, but he >> specified a reply to the report and not the report itself, as expected >> by regzbot (I'm taken back and forth for a while already if that's a >> good or bad idea). And that was not Greg's but my fault, as I had given >> him the wrong link here: >> https://lore.kernel.org/r/YcH2w9jmGnqUMWp4@kroah.com/ > > Sorry about that, I tried! :( Many thx. And as mentioned: it was my fault :-/ > Keep up the great work, Will do, thx for saying this, there are sometimes tough days where things like this help. :-D > we'll get the workflow down yet. FWIW, regzbot in a few cases already completely worked as intended to. But yeah, things like this always take a while to get settled. My biggest problem is: many developers don't place the Link: tags. I obviously expected that up to a point. But what I didn't expect: so much opposition to place them, because quite a few developers think they are reserved for maintainers, as they are only meant for linking to the submission of the applied patch; a few also think others tags should be needed for linking to bugs. My proposed "introduce the commit message tags 'Reported:' and 'Posted:'" patch likely would have helped here, but didn't get any traction :-/ https://firstname.lastname@example.org/ Maybe that was partly due to the stupid mixup in the subject of the cover letter, but whatever. So I guess I'll drop the bold idea. I consider proposing to create "Reported: <url>" while leaving ambiguous Link: alone, which will help my case. Note sure if I also should propose to drop "Reported-by" at the same time, which makes things easier for developers, as that tag can only be set after asking the reporter. Ciao, Thorsten
next prev parent reply other threads:[~2021-12-22 8:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com/> 2021-12-16 9:22 ` [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference Thorsten Leemhuis 2021-12-16 11:47 ` Heikki Krogerus 2021-12-21 18:06 ` [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference #forregzbot Thorsten Leemhuis 2021-12-22 6:32 ` Greg KH 2021-12-22 8:37 ` Thorsten Leemhuis [this message] 2021-12-22 9:02 ` Greg KH 2021-12-22 9:39 ` Thorsten Leemhuis
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 \ --subject='Re: [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference #forregzbot' \ /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).