mm-commits.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,wy@wyuan.org,users@kernel.org,
	skhan@linuxfoundation.org,si.yanteng@linux.dev,rdunlap@infradead.org,
	petr.pavlu@suse.com,joe@perches.com,federico.vaga@vaga.pv.it,
	dzm91@hust.edu.cn,corbet@lwn.net,chenyou910331@gmail.com,
	carlos.bilbao@kernel.org,avadhut.naik@amd.com,alexs@kernel.org,
	akiyks@gmail.com,konstantin@linuxfoundation.org,akpm@linux-foundation.org
Subject: [merged mm-nonmm-hotfixes-stable] docs-submitting-patches-make-lkml-a-list-of-last-resort-again.patch removed from -mm tree
Date: Tue, 17 Nov 2026 21:41:53 -0800	[thread overview]
Message-ID: <20261118054153.CCDE91F000D0@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: docs: submitting-patches: make LKML a list of last resort again
has been removed from the -mm tree.  Its filename was
     docs-submitting-patches-make-lkml-a-list-of-last-resort-again.patch

This patch was dropped because it was merged into the mm-nonmm-hotfixes-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: docs: submitting-patches: make LKML a list of last resort again
Date: Fri, 13 Nov 2026 18:02:46 -0500

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.

Link: https://lore.kernel.org/20261113-get-maintainer-the-rest-fallback-v3-2-36ee5a3e8d13@linuxfoundation.org
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Suggested-by: Petr Pavlu <petr.pavlu@suse.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Joe Perches <joe@perches.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Akira Yokosawa <akiyks@gmail.com>
Cc: Carlos Bilbao <carlos.bilbao@kernel.org>
Cc: Avadhut Naik <avadhut.naik@amd.com>
Cc: Alex Shi <alexs@kernel.org>
Cc: Yanteng Si <si.yanteng@linux.dev>
Cc: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: Weijie Yuan <wy@wyuan.org>
Cc: <users@kernel.org>

 Documentation/process/submitting-patches.rst |    9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

--- a/Documentation/process/submitting-patches.rst~docs-submitting-patches-make-lkml-a-list-of-last-resort-again
+++ a/Documentation/process/submitting-patches.rst
@@ -239,9 +239,12 @@ patches as arguments to scripts/get_main
 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
_

Patches currently in -mm which might be from konstantin@linuxfoundation.org are



                 reply	other threads:[~2026-11-18  5:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261118054153.CCDE91F000D0@smtp.kernel.org \
    --to=akpm@linux-foundation.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=mm-commits@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=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;
as well as URLs for NNTP newsgroup(s).