From: Randy Dunlap <rdunlap@infradead.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Joe Perches <joe@perches.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.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 2/2] docs: submitting-patches: make LKML a list of last resort again
Date: Fri, 13 Nov 2026 17:54:04 -0800 [thread overview]
Message-ID: <ccfe6cc4-507f-4e54-890d-91da75de11fc@infradead.org> (raw)
In-Reply-To: <20261113-get-maintainer-the-rest-fallback-v3-2-36ee5a3e8d13@linuxfoundation.org>
On 11/13/26 3:02 PM, Konstantin Ryabitsev wrote:
> Commit 77167b966b7e ("docs: submitting-patches: clarify the role of
> LKML") changed the documentation to say that all patches should be sent
> to LKML by default, because get_maintainer.pl always suggested it.
>
> Now that get_maintainer.pl only falls back to THE REST when no other
> matching section provides a mailing list, update the documentation to
> match: send patches to the subsystem-specific list, and use LKML only
> when there isn't one.
>
> Suggested-by: Petr Pavlu <petr.pavlu@suse.com>
> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/process/submitting-patches.rst | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index f271d7413f72..85ba046d66fb 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -239,9 +239,12 @@ patches as arguments to scripts/get_maintainer.pl). If you cannot find a
> maintainer for the subsystem you are working on, Andrew Morton
> (akpm@linux-foundation.org) serves as a maintainer of last resort.
>
> -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.
> +You should also normally choose at least one mailing list to receive a copy of
> +your patch set. Look in the MAINTAINERS file for a subsystem-specific list;
> +your patch will probably get more attention there.
> +linux-kernel@vger.kernel.org functions as a list of last resort for patches
> +that do not have a subsystem-specific list. Please do not spam unrelated lists
> +and unrelated people, though.
>
> Many kernel-related lists are hosted at kernel.org; you can find a list
> of them at https://subspace.kernel.org. There are kernel-related lists
>
--
~Randy
next prev parent reply other threads:[~2026-11-14 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:02 [PATCH v3 0/2] get_maintainer: stop sending every patch to LKML 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 [this message]
2026-11-14 2:59 ` [PATCH v3 0/2] get_maintainer: stop sending every patch to LKML Joe Perches
2026-11-14 3:49 ` 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=ccfe6cc4-507f-4e54-890d-91da75de11fc@infradead.org \
--to=rdunlap@infradead.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=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--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®