From: Jonathan Corbet <corbet@lwn.net>
To: "Bird, Tim" <Tim.Bird@sony.com>,
Greg KroahHartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: stable-kernel-rules: fix typo sent->send
Date: Thu, 02 May 2024 10:21:08 -0600 [thread overview]
Message-ID: <877cgc6v7v.fsf@meer.lwn.net> (raw)
In-Reply-To: <SA3PR13MB63726A746C847D7C0919C25BFD162@SA3PR13MB6372.namprd13.prod.outlook.com>
"Bird, Tim" <Tim.Bird@sony.com> writes:
> Change 'sent' to 'send'
>
> Signed-off-by: Tim Bird <tim.bird@sony.com>
> ---
> Documentation/process/stable-kernel-rules.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index 1704f1c686d0..3178bef6fca3 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -78,7 +78,7 @@ in the sign-off area. Once the patch is mainlined it will be applied to the
> stable tree without anything else needing to be done by the author or
> subsystem maintainer.
>
> -To sent additional instructions to the stable team, use a shell-style inline
> +To send additional instructions to the stable team, use a shell-style inline
> comment:
Applied, thanks.
jon
prev parent reply other threads:[~2024-05-02 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 23:18 [PATCH] docs: stable-kernel-rules: fix typo sent->send Bird, Tim
2024-04-27 10:09 ` Greg KroahHartman
2024-04-30 18:12 ` Bird, Tim
2024-04-27 10:25 ` Bagas Sanjaya
2024-05-02 16:21 ` 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=877cgc6v7v.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Tim.Bird@sony.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=workflows@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 read-only IMAP folder(s) and NNTP newsgroup(s).