From: Jonathan Corbet <corbet@lwn.net>
To: Hannu Hartikainen <hannu@hrtk.in>, linux-doc@vger.kernel.org
Cc: Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, Hannu Hartikainen <hannu@hrtk.in>
Subject: Re: [PATCH] docs: submitting-patches: clarify the role of LKML
Date: Sun, 25 Jul 2021 14:46:09 -0600 [thread overview]
Message-ID: <87sg02t94e.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210707133634.286840-1-hannu@hrtk.in>
Hannu Hartikainen <hannu@hrtk.in> writes:
> The documentation previously stated that LKML should be used as *last
> resort*. However, scripts/get_maintainer.pl always suggests it and in a
> discussion about changing that[0] it turned out that LKML should in fact
> receive all patches.
>
> Update documentation to make it clear that all patches should be sent to
> LKML by default, in addition to any subsystem-specific lists.
>
> [0]: https://lore.kernel.org/lkml/19a701a8d5837088aa7d8ba594c228c0e040e747.camel@perches.com/
>
> Signed-off-by: Hannu Hartikainen <hannu@hrtk.in>
> ---
> Documentation/process/submitting-patches.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2021-07-25 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:36 [PATCH] docs: submitting-patches: clarify the role of LKML Hannu Hartikainen
2021-07-25 20:46 ` Jonathan Corbet [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=87sg02t94e.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=hannu@hrtk.in \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).