From: Andrew Morton <akpm@linux-foundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@kernel.org, ksummit@lists.linux.dev
Subject: Re: slowly decommission bugzilla? (was: Re: kernel.org tooling update)
Date: Thu, 26 Feb 2026 09:04:25 -0800 [thread overview]
Message-ID: <20260226090425.11bb585062783c0e1fcf0b32@linux-foundation.org> (raw)
In-Reply-To: <b93eae05-5e40-42f0-8256-d46d411008a4@leemhuis.info>
On Thu, 26 Feb 2026 09:44:32 +0100 Thorsten Leemhuis <linux@leemhuis.info> wrote:
> * Create a new front page that tells users that they most likely are in
> the wrong place. The text could look like this:
I think it would be best, please. Bugzilla has never worked for us.
> """
> Welcome! Note: The kernel.org bugzilla is slowly being decommissioned!
>
> This bug tracker is a kind of failed experiment, which at the same time
> still is useful sometimes and thus for now kept alive. Due to this and
> how vendors utilize the Linux kernel, you are most likely in the wrong
> place to report your bug.
>
> To find the right place, check the Linux kernel's [MAINTAINERS
> file](https://docs.kernel.org/process/maintainers.html). Most of the
> time it will tell you to report bugs by email with some mailing lists in
> CC. Bugs with all the kernel's modern graphics drivers, on the other
> hand, [must be submitted to a Gitlab
> instance](https://gitlab.freedesktop.org/drm) – and a small number of
> subsystems want reports in issue trackers of dedicated Github projects
> or this bug tracker.
Perhaps point people at scripts/get_maintainer.pl
Or heck, add a front-end to get_maintainer right here in this web page.
People paste in a pathname and it spits back a bunch of email
addresses.
> For more details on this and reporting Linux kernel bugs in general, see
> the [official step-by-step guide on reporting
> issues](https://docs.kernel.org/admin-guide/reporting-issues.html#step-by-step-guide-how-to-report-issues-to-the-kernel-maintainers).
> It covers all the important aspects, including one that is often missed:
>
> In case somebody else compiled your Linux kernel, you most likely have
> to report bugs to said vendor – like Linux Mint, Red Hat, Ubuntu, or
> SUSE. That is because the majority of the Linux developers only care for
> bugs occurring with kernels built from Linux sources that are pristine
> (aka "vanilla") or nearly so. Kernels using independently developed
> kernel modules are therefore just as unsuitable for reporting bugs upstream.
prev parent reply other threads:[~2026-02-26 17:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 4:48 kernel.org tooling update Konstantin Ryabitsev
2025-12-10 8:11 ` Mauro Carvalho Chehab
2025-12-10 13:30 ` Thorsten Leemhuis
2025-12-11 3:04 ` Theodore Tso
2025-12-12 23:48 ` Stephen Hemminger
2025-12-12 23:54 ` Randy Dunlap
2025-12-16 16:21 ` Lukas Wunner
2025-12-16 20:33 ` Jeff Johnson
2025-12-17 0:47 ` Mario Limonciello
2025-12-18 13:37 ` Jani Nikula
2025-12-18 14:09 ` Mario Limonciello
2026-01-23 9:19 ` Web of Trust work [Was: kernel.org tooling update] Uwe Kleine-König
2026-01-23 9:29 ` Greg KH
2026-01-23 11:47 ` Mauro Carvalho Chehab
2026-01-23 11:58 ` Greg KH
2026-01-23 12:24 ` Mauro Carvalho Chehab
2026-01-23 12:29 ` Greg KH
2026-01-23 13:57 ` Konstantin Ryabitsev
2026-01-23 16:24 ` James Bottomley
2026-01-23 16:33 ` Greg KH
2026-01-23 16:42 ` Joe Perches
2026-01-23 17:00 ` Steven Rostedt
2026-01-23 17:23 ` James Bottomley
2026-01-23 18:23 ` Konstantin Ryabitsev
2026-01-23 21:12 ` Uwe Kleine-König
2026-01-26 16:23 ` Konstantin Ryabitsev
2026-01-26 17:32 ` Uwe Kleine-König
2026-01-26 21:01 ` Konstantin Ryabitsev
2026-01-26 23:23 ` James Bottomley
2026-01-27 8:39 ` Uwe Kleine-König
2026-01-27 21:08 ` Linus Torvalds
2026-02-04 10:49 ` Uwe Kleine-König
2026-02-05 10:14 ` James Bottomley
2026-02-05 18:07 ` Uwe Kleine-König
2026-02-05 18:23 ` Konstantin Ryabitsev
2026-01-26 23:33 ` Mauro Carvalho Chehab
2026-01-26 23:06 ` Mauro Carvalho Chehab
2026-01-23 21:38 ` James Bottomley
2026-01-23 22:55 ` Mauro Carvalho Chehab
2026-01-23 16:38 ` Konstantin Ryabitsev
2026-01-23 17:02 ` Paul Moore
2026-01-23 18:42 ` kernel.org tooling update Randy Dunlap
2026-02-26 8:44 ` slowly decommission bugzilla? (was: Re: kernel.org tooling update) Thorsten Leemhuis
2026-02-26 14:40 ` Andrew G. Morgan
2026-02-26 17:04 ` Andrew Morton [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 \
--in-reply-to=20260226090425.11bb585062783c0e1fcf0b32@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=linux@leemhuis.info \
--cc=users@kernel.org \
/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
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