From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Joe Perches <joe@perches.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.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 v2 0/2] get_maintainer: stop sending every patch to LKML
Date: Sun, 1 Nov 2026 09:42:08 -0500 [thread overview]
Message-ID: <20261101-inescapable-vivacious-shoebill-5b7ebb@lemur> (raw)
In-Reply-To: <20261020-get-maintainer-the-rest-fallback-v2-0-162aea473488@linuxfoundation.org>
On Tue, Oct 20, 2026 at 11:35:24AM -0400, 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:
>
> - 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 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.
Linus, it looks like everyone is on board with this change, but it never made
it into any pull request. Will you consider merging this one directly for 7.4
rc-1? This ought to do it:
b4 shazam -S 20261020-get-maintainer-the-rest-fallback-v2-0-162aea473488@linuxfoundation.org
With the ever-increasing volume of patches sent in and Gmail's obtuse "you're
sending us too much mail, back off" attitude, this is becoming urgent.
Thanks,
-K
next prev parent reply other threads:[~2026-11-01 14:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:35 Konstantin Ryabitsev
2026-10-20 15:35 ` [PATCH v2 1/2] get_maintainer: only use THE REST as a fallback Konstantin Ryabitsev
2026-10-20 15:47 ` Joe Perches
2026-10-20 15:52 ` Konstantin Ryabitsev
2026-10-20 16:39 ` Joe Perches
2026-10-20 15:35 ` [PATCH v2 2/2] docs: submitting-patches: make LKML a list of last resort again Konstantin Ryabitsev
2026-10-20 16:58 ` Randy Dunlap
2026-10-21 6:29 ` Krzysztof Kozlowski
2026-10-21 6:48 ` Greg KH
2026-10-21 8:33 ` Lee Jones
2026-10-21 20:33 ` Jiri Kosina
2026-10-20 15:53 ` [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML Joe Perches
2026-10-20 18:51 ` Theodore Tso
2026-10-21 9:13 ` Geert Uytterhoeven
2026-10-20 16:44 ` Weijie Yuan
2026-11-01 14:42 ` Konstantin Ryabitsev [this message]
2026-11-02 9:32 ` David Laight
2026-11-02 14:12 ` Konstantin Ryabitsev
2026-11-02 14:18 ` Rafael J. Wysocki (Intel)
2026-11-02 14:34 ` Jonathan Corbet
2026-11-02 14:45 ` Rafael J. Wysocki (Intel)
2026-11-02 17:15 ` Sean Christopherson
2026-11-02 15:05 ` David Laight
2026-11-02 15:47 ` Jonathan Corbet
2026-11-02 16:10 ` Joe Perches
2026-11-02 16:23 ` Konstantin Ryabitsev
2026-11-02 16:20 ` Konstantin Ryabitsev
2026-11-02 16:24 ` Geert Uytterhoeven
2026-11-02 17:17 ` David Laight
2026-11-02 17:56 ` Konstantin Ryabitsev
2026-11-02 18:25 ` Rafael J. Wysocki (Intel)
2026-11-02 19:31 ` David Laight
2026-11-03 0:16 ` Dongliang Mu
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=20261101-inescapable-vivacious-shoebill-5b7ebb@lemur \
--to=konstantin@linuxfoundation.org \
--cc=akiyks@gmail.com \
--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=joe@perches.com \
--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=torvalds@linux-foundation.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®