All of lore.kernel.org
 help / color / mirror / Atom feed
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.

  parent reply	other threads:[~2026-02-26 17:04 UTC|newest]

Thread overview: 117+ 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-03-08  7:21     ` Uwe Kleine-König
2026-03-08 10:24       ` Greg KH
2026-03-18 14:02         ` Greg KH
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]
2026-02-27 11:07     ` Jani Nikula
2026-02-27 15:16     ` Steven Rostedt
2026-02-27 15:18       ` Mark Brown
2026-02-27 15:44         ` Steven Rostedt
2026-02-27 15:18       ` slowly decommission bugzilla? Sven Peter
2026-02-27 15:35       ` slowly decommission bugzilla? (was: Re: kernel.org tooling update) Richard Weinberger
2026-02-27 16:00         ` Geert Uytterhoeven
2026-02-27 16:22           ` Richard Weinberger
2026-02-27 16:29             ` Peter Zijlstra
2026-02-27 17:07               ` James Bottomley
2026-02-28 13:41             ` slowly decommission bugzilla? Thorsten Leemhuis
2026-02-28 15:17               ` Richard Weinberger
2026-02-28 17:40                 ` Linus Torvalds
2026-02-28 18:29                   ` Richard Weinberger
2026-02-28 20:26                     ` Steven Rostedt
2026-02-28 20:28                       ` Richard Weinberger
2026-02-28 20:56                         ` Steven Rostedt
2026-03-01 15:23                           ` Sasha Levin
2026-03-01 15:35                             ` Laurent Pinchart
2026-03-01 15:42                               ` Sasha Levin
2026-03-01 16:13                                 ` Laurent Pinchart
2026-03-01 16:27                                   ` Sasha Levin
2026-03-06 15:01                                     ` Laurent Pinchart
2026-03-07 16:19                                       ` Sasha Levin
2026-03-01 16:15                               ` James Bottomley
2026-03-01 16:49                                 ` Laurent Pinchart
2026-03-02  8:55                                 ` Mauro Carvalho Chehab
2026-03-01 17:33                               ` Linus Torvalds
2026-03-02 20:28                                 ` [RFC] kallsyms: embed source file:line info in kernel stack traces Sasha Levin
2026-03-03  5:39                                   ` Alexey Dobriyan
2026-03-03 12:44                                     ` Sasha Levin
2026-03-03 13:17                                     ` Steven Rostedt
2026-03-03 16:35                                       ` Sasha Levin
2026-03-06 15:22                                         ` Laurent Pinchart
2026-03-03 19:09                                       ` Alexey Dobriyan
2026-03-03  6:26                                   ` Richard Weinberger
2026-03-03  6:48                                     ` Tomasz Figa
2026-03-03  9:04                                       ` Vlastimil Babka (SUSE)
2026-03-03 12:45                                         ` Sasha Levin
2026-03-03  8:11                                     ` Geert Uytterhoeven
2026-03-03  9:31                                       ` Jiri Slaby
2026-03-03 12:47                                         ` Sasha Levin
2026-03-03 12:58                                           ` James Bottomley
2026-03-03 13:08                                             ` Jürgen Groß
2026-03-03  8:09                                   ` Geert Uytterhoeven
2026-03-03 22:44                                   ` Helge Deller
2026-03-03 22:47                                     ` Sasha Levin
2026-03-01 16:01                             ` slowly decommission bugzilla? James Bottomley
2026-03-01 16:16                               ` Sasha Levin
2026-03-01 16:25                                 ` James Bottomley
2026-03-01 16:33                                   ` Sasha Levin
2026-03-06 10:37                 ` Richard Weinberger
2026-03-06 10:44                   ` Geert Uytterhoeven
2026-03-15 14:58                     ` Richard Weinberger
2026-03-16 11:28                       ` Greg KH
2026-03-16 21:56                         ` Richard Weinberger
2026-03-17  7:51                           ` Greg Kroah-Hartman
2026-04-02  4:59   ` slowly decommission bugzilla? (was: Re: kernel.org tooling update) Konstantin Ryabitsev
2026-04-02 13:07     ` Theodore Tso
2026-04-02 13:28       ` Konstantin Ryabitsev
2026-04-02 14:08         ` Theodore Tso
2026-04-02 14:21           ` Konstantin Ryabitsev
2026-04-02 14:49         ` Steven Rostedt
2026-04-02 13:51       ` James Bottomley
2026-04-02 13:42     ` slowly decommission bugzilla? Thorsten Leemhuis
2026-04-02 14:04       ` Konstantin Ryabitsev
2026-04-02 14:15         ` Richard Weinberger
2026-04-02 15:45       ` Laurent Pinchart
2026-04-02 16:04         ` 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 \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.