Re: [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference #forregzbot

[Greg KH <greg@kroah.com>]

On Wed, Dec 22, 2021 at 09:37:55AM +0100, Thorsten Leemhuis wrote:
> 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.

Hah, I can't even get developers to add a Fixes: or a Cc: stable tag,
trying to get them to add a Link: tag to a lore reference is going to be
an uphill battle.

Right now, the best thing we have is the git hook that auto-adds the
Link: tag that points to the lore thread where the patch came from.
Maintainers don't have the energy or time to add anything other than
that, so I think you just might have to rely on Fixes: for a while.

> My proposed "introduce the commit message tags 'Reported:' and
> 'Posted:'" patch likely would have helped here, but didn't get any
> traction :-/
> https://lore.kernel.org/lkml/c6724c7fb534a46e095e6aef13d996ed9589e578.1639042966.git.linux@leemhuis.info/
> 
> 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.

Nah, I add "Reported-by:" all the time without asking for explicit
permission, relying on the public email instead.  If there was some way
to automate the Reported: tag, maybe it could be used, but again, that's
a lot of manual work to do, which is going to be a hard sell.

thanks,

greg k-h