From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
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 19:49:15 -0800 [thread overview]
Message-ID: <20261113194915.a48a1a3778464348773dffd4@linux-foundation.org> (raw)
In-Reply-To: <0825b89ca1dfe1ff20090d6dfdbb725b3f471d65.camel@perches.com>
On Fri, 13 Nov 2026 18:59:50 -0800 Joe Perches <joe@perches.com> wrote:
> 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?
Sure, added to mm.git's 7.4-rcX hotfixes queue, thanks.
prev parent reply other threads:[~2026-11-14 3:49 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 ` [PATCH v3 0/2] get_maintainer: stop sending every patch to LKML Joe Perches
2026-11-14 3:49 ` Andrew Morton [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=20261113194915.a48a1a3778464348773dffd4@linux-foundation.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=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®