mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dongliang Mu <dzm91@hust.edu.cn>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.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>,
	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: Tue, 3 Nov 2026 08:16:13 +0800	[thread overview]
Message-ID: <deea3016-1322-4bd2-9c03-05e9e32b486d@hust.edu.cn> (raw)
In-Reply-To: <20261020-get-maintainer-the-rest-fallback-v2-0-162aea473488@linuxfoundation.org>


On 10/20/26 11:35 PM, 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.
>
> 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.

Will update the zh_CN translation once the patchset is accepted.

Dongliang Mu

>
> ---
> 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: c03c1a14507dfaf8b856c2608f9ac216021fc222
> 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>


      parent reply	other threads:[~2026-11-03  0:16 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
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 [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=deea3016-1322-4bd2-9c03-05e9e32b486d@hust.edu.cn \
    --to=dzm91@hust.edu.cn \
    --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=federico.vaga@vaga.pv.it \
    --cc=joe@perches.com \
    --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®