mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Pavlu <petr.pavlu@suse.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, users@kernel.org
Subject: Re: [PATCH] get_maintainer: only use THE REST as a fallback
Date: Thu, 8 Oct 2026 15:39:53 +0200	[thread overview]
Message-ID: <92d5ec39-6a0e-437e-a03d-b1d2c0ec24cb@suse.com> (raw)
In-Reply-To: <20261008-get-maintainer-the-rest-fallback-v1-1-7d26d0b7aa34@linuxfoundation.org>

On 10/8/26 2:51 PM, Konstantin Ryabitsev wrote:
> THE REST matches every file in the tree via "F: *" and "F: */", so
> get_maintainer.pl currently adds linux-kernel@vger.kernel.org to every
> patch, regardless of whether the touched files already belong to a
> subsystem with its own mailing list.
> 
> Only add THE REST for a file when no other matching section provides a
> mailing list for it. Files that match no section, or only sections
> without an L: entry, still fall back to THE REST, so every patch keeps
> reaching at least one public list.
> 
> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> ---
> LKML has become mostly a firehose of patches that are already going to a
> subsystem list. The reason is THE REST: it matches every file in the
> tree, so get_maintainer.pl adds linux-kernel@vger.kernel.org to every
> single patch. During the week of Oct 1-7, 2026:
> 
>   - LKML carried 13,641 messages (~1,950/day), 90% of which were also
>     sent to at least one other list;
>   - with ~2,100 subscribers, that is about 29 million deliveries per
>     week for LKML alone.
> 
> This issue came up during the 2026 Maintainer Summit and the consensus
> was that "always include linux-kernel for every patch" was never the
> intent.
> 
> This patch makes THE REST a fallback as initially intended: it is only
> added for a file when no other matching MAINTAINERS section provides a
> mailing list for it.

Documentation/process/submitting-patches.rst currently says:

| linux-kernel@vger.kernel.org should be used by default for all patches, but the
| volume on that list has caused a number of developers to tune it out.  Please
| do not spam unrelated lists and unrelated people, though.

If the behavior of scripts/get_maintainer.pl is changed, it would be
good to update this documentation accordingly, possibly by simply
reverting commit 77167b966b7e ("docs: submitting-patches: clarify the
role of LKML").

-- 
Thanks,
Petr

  parent reply	other threads:[~2026-10-08 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:51 Konstantin Ryabitsev
2026-10-08 13:03 ` Jason A. Donenfeld
2026-10-08 13:10   ` Konstantin Ryabitsev
2026-10-08 13:22     ` Matthieu Baerts
2026-10-08 14:05       ` Konstantin Ryabitsev
2026-10-08 16:04         ` Matthieu Baerts
2026-10-09 16:41     ` Jason A. Donenfeld
2026-10-08 13:15 ` Jürgen Groß
2026-10-08 14:02   ` Konstantin Ryabitsev
2026-10-09 12:24   ` Jason Gunthorpe
2026-10-09 18:37   ` Willy Tarreau
2026-10-08 13:15 ` Michael S. Tsirkin
2026-10-08 13:39 ` Petr Pavlu [this message]
2026-10-08 14:06   ` Konstantin Ryabitsev
2026-10-09 16:25 ` Joe Perches

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=92d5ec39-6a0e-437e-a03d-b1d2c0ec24cb@suse.com \
    --to=petr.pavlu@suse.com \
    --cc=joe@perches.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®