archive mirror
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <>
To: Jani Nikula <>,
	Linux Kernel Mailing List <>,
Subject: Re: [PATCH v1 (RFC)] docs: discourage users from using
Date: Mon, 8 Nov 2021 12:03:20 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/8/21 11:43, Jani Nikula wrote:
> On Fri, 05 Nov 2021, "Artem S. Tashkinov" <> wrote:
>> Let me continue.
>> Here's something which is really bad for
>> People _continue_ to file bug reports for graphics drivers in Linux and
>> we don't even have proper components for it, only
>> Video (AGP) - What? AGP has been dead for a decade.
>> Video (DRI - Non Intel)  - what? Isn't it an's feature, not kernel's?
>> Video (Other)
>> This is a complete and total clusterjoy.
> FWIW, for Intel graphics (i915) we don't want any bug reports at
> We've migrated away more than five years ago. The
> "Video (DRI - Intel)" component was closed for new bugs around that

 From my initial message:

2.6 You're under the impression that users will read this wonderful
document (reporting-bugs.rst). They will *not*, they will google for
"report bug linux kernel" and find

2) To integrate the first three with
and automatically crosspost over there.

It does *not* help one bit that we have different bug trackers and
mailing lists for a *single* component which is the kernel. No other
software project under the sun makes the user rack their head trying to
understand how and where to post bug reports.

And then like I've mentioned earlier:

2.1 Tons of messages in various kernel related mailing lists have zero
replies and are not acted upon in any way or shape

2.2 There's no sense of accountability, no way to see what are the
current issues, what's resolved or not

2.3 Users have an extremely hard time looking for bug reports which are
spread along God knows where

2.4 It's impossible to follow up on such messages except when you were
subscribed to the original mailing list, IOW just impossible

2.5 It's extremely difficult to collaborate since e-mail totally sucks
when it comes to long discussions.

The Linux kernel bug reporting process is a complete clusterfuck and it
looks like no one cares at all. The consensus is "the harder it is, the
better" since unreported bugs means less work, accountability and

The fact that no one from FSF has replied to any of my messages is a
further confirmation. Budget ~$2 million in FY 2019. I guess two million
bucks are not enough to take proper care of the most important FSF project.

Can we shut down completely? In its current form
it's nothing but disgrace.

> time, the description points at as does MAINTAINERS:
> INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets)
> B:
> BR,
> Jani.

  reply	other threads:[~2021-11-08 12:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 12:10 [PATCH v1 (RFC)] docs: discourage users from using Thorsten Leemhuis
2021-01-11 18:14 ` Randy Dunlap
2021-01-11 18:55   ` Thorsten Leemhuis
2021-01-11 23:42     ` Randy Dunlap
2021-01-12 17:34       ` Thorsten Leemhuis
2021-01-11 19:48 ` Konstantin Ryabitsev
2021-01-12 19:09   ` Thorsten Leemhuis
2021-01-13 11:17     ` Jani Nikula
2021-01-14 19:18       ` Konstantin Ryabitsev
2021-11-05 14:36 ` Artem S. Tashkinov
2021-11-05 14:42   ` Matthew Wilcox
2021-11-05 14:59     ` Artem S. Tashkinov
2021-11-08 11:43   ` Jani Nikula
2021-11-08 12:03     ` Artem S. Tashkinov [this message]
2021-11-08 13:00       ` Jani Nikula
2021-11-08 13:17         ` Artem S. Tashkinov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).