From: Joe Perches <joe@perches.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, users@kernel.org,
Federico Vaga <federico.vaga@vaga.pv.it>,
Akira Yokosawa <akiyks@gmail.com>,
Carlos Bilbao <carlos.bilbao@kernel.org>,
Avadhut Naik <avadhut.naik@amd.com>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Chen-Yu Yeh <chenyou910331@gmail.com>, Weijie Yuan <wy@wyuan.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
Petr Pavlu <petr.pavlu@suse.com>
Subject: Re: [PATCH v3 0/2] get_maintainer: stop sending every patch to LKML
Date: Fri, 13 Nov 2026 18:59:50 -0800 [thread overview]
Message-ID: <0825b89ca1dfe1ff20090d6dfdbb725b3f471d65.camel@perches.com> (raw)
In-Reply-To: <20261113-get-maintainer-the-rest-fallback-v3-0-36ee5a3e8d13@linuxfoundation.org>
On Fri, 2026-11-13 at 18:02 -0500, Konstantin Ryabitsev wrote:
> 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:
Andrew can you please get this upstream?
>
> - 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 problem is becoming urgent and untenable. The increased volume of
> patches sent using AI tooling has resulted in dramatically higher
> delivery queues and if this change is not implemented, we will have to
> start force-unsubscribing addresses that do not show any developer
> activity or use similar drastic measures.
>
> 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 series 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 that get_maintainer.pl would actually output for it.
> Patch 2 updates submitting-patches.rst, which currently tells submitters
> to send every patch to LKML.
>
> Several v1 reviewers asked for a catch-all list that would keep carrying
> every patch for those who want to follow all kernel development. That
> is a worthwhile discussion, but it is separate from this series, which
> only restores THE REST to its original role.
>
> Translation maintainers are Cc'd because the it_IT, ja_JP, sp_SP, zh_CN
> and zh_TW versions of submitting-patches.rst carry the same "send every
> patch to LKML" advice and will need a follow-up update once the English
> text is settled.
>
> ---
> Changes in v3:
> - Rebased on v7.4-rc2
> - Update the cover to specify that this is urgent
> - Link to v2: https://patch.msgid.link/20261020-get-maintainer-the-rest-fallback-v2-0-162aea473488@linuxfoundation.org
>
> Changes in v2:
> - Don't count subscribers-only lists (or moderated lists with
> --no-moderated) as a destination, since get_maintainer.pl doesn't
> output them; v1 sent patches to e.g. fs/squashfs/ to no list at all
> - Add submitting-patches.rst update describing LKML as the list of last
> resort (Petr Pavlu)
> - Rebase on v7.3
> - Link to v1: https://patch.msgid.link/20261008-get-maintainer-the-rest-fallback-v1-1-7d26d0b7aa34@linuxfoundation.org
>
> ---
> Konstantin Ryabitsev (2):
> get_maintainer: only use THE REST as a fallback
> docs: submitting-patches: make LKML a list of last resort again
>
> Documentation/process/submitting-patches.rst | 9 ++++--
> scripts/get_maintainer.pl | 43 ++++++++++++++++++++++++++++
> 2 files changed, 49 insertions(+), 3 deletions(-)
> ---
> base-commit: 7475ea8b58616b33c04afb976cf0fbaad9dd63fb
> base-tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> change-id: 20261008-get-maintainer-the-rest-fallback-6655e8a648d4
>
> Best regards,
> --
> Konstantin Ryabitsev <konstantin@linuxfoundation.org>
next prev parent reply other threads:[~2026-11-14 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:02 Konstantin Ryabitsev
2026-11-13 23:02 ` [PATCH v3 1/2] get_maintainer: only use THE REST as a fallback Konstantin Ryabitsev
2026-11-13 23:02 ` [PATCH v3 2/2] docs: submitting-patches: make LKML a list of last resort again Konstantin Ryabitsev
2026-11-14 1:54 ` Randy Dunlap
2026-11-14 2:59 ` Joe Perches [this message]
2026-11-14 3:49 ` [PATCH v3 0/2] get_maintainer: stop sending every patch to LKML Andrew Morton
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=0825b89ca1dfe1ff20090d6dfdbb725b3f471d65.camel@perches.com \
--to=joe@perches.com \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=federico.vaga@vaga.pv.it \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=users@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=wy@wyuan.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®