Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"

[Artem S. Tashkinov]

On 10/1/22 10:57, Thorsten Leemhuis wrote:
> On 01.10.22 12:47, Artem S. Tashkinov wrote:
> > On 10/1/22 10:39, Greg KH wrote:
> > > On Sat, Oct 01, 2022 at 10:30:22AM +0000, Artem S. Tashkinov wrote:
>
> > > > I have a 20+ years experience in IT and some kernel issues are just
> > > > baffling in terms of trying to understand what to do about them.
> > > >
> > > > Here's an example: https://bugzilla.kernel.org/show_bug.cgi?id=216274
> > > >
> > > > What should I do about that? Who's responsible for this? Who should I
> > > > CC?
> > >
> > > Input subsystem.
> >
> > It's great you've replied immediately, what about hundreds or even
> > thousands of other bug reports where people have no clue who has to be
> > CC'ed?
>
> Quoting from https://docs.kernel.org/admin-guide/reporting-issues.html:
>
> "[...] try your best guess which kernel part might be causing the issue.
> Check the MAINTAINERS file [...] In case tricks like these don’t bring
> you any further, try to search the internet on how to narrow down the
> driver or subsystem in question. And if you are unsure which it is: just
> try your best guess, somebody will help you if you guessed poorly. [...]"
>
> HTH, Ciao, Thorsten

Absolute most people:

* Will never read this document
* Will not be able to "search the internet on how to narrow down the
driver or subsystem in question"

Lastly "unsure which it is: just try your best guess, somebody will help
you if you guessed poorly", so send a message to LKML and hope someone
will reply? This generally does not work. LKML is such a high volume
mailing list, individual messages get lost right away.

Regards,
Artem