From: Jonathan Corbet <corbet@lwn.net>
To: Rong Tao <rtoax@foxmail.com>, krzysztof.kozlowski@linaro.org
Cc: erik@kryo.se, jkosina@suse.cz, konstantin@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@leemhuis.info, lkp@intel.com, ojeda@kernel.org,
rdunlap@infradead.org, rongtao@cestc.cn, rtoax@foxmail.com,
tglx@linutronix.de, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v2] Documentation: process/submitting-patches: misspelling "mesages"
Date: Wed, 21 Sep 2022 13:58:53 -0600 [thread overview]
Message-ID: <8735ckwlc2.fsf@meer.lwn.net> (raw)
In-Reply-To: <tencent_924BF0B25425E2D5673409D1CF604F682505@qq.com>
Rong Tao <rtoax@foxmail.com> writes:
> Fix spelling mistakes, "mesages" should be spelled "messages".
>
> Signed-off-by: Rong Tao <rtoax@foxmail.com>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/process/submitting-patches.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index be49d8f2601b..7dc94555417d 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -715,8 +715,8 @@ references.
>
> .. _backtraces:
>
> -Backtraces in commit mesages
> -^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> +Backtraces in commit messages
> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
Applied, thanks.
jon
next prev parent reply other threads:[~2022-09-21 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 5:11 [PATCH] Documentation: process/submitting-patches: misspelling "mesages" Rong Tao
2022-09-13 8:40 ` Krzysztof Kozlowski
2022-09-13 13:55 ` lkp report WARNING: Title underline too short Rong Tao
2022-09-13 14:14 ` Krzysztof Kozlowski
2022-09-14 0:33 ` [PATCH v2] Documentation: process/submitting-patches: misspelling "mesages" Rong Tao
2022-09-21 19:58 ` Jonathan Corbet [this message]
2022-09-14 2:58 ` Rong Tao
2022-09-13 13:40 ` [PATCH] " Bagas Sanjaya
2022-09-13 14:02 ` Rong Tao
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=8735ckwlc2.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=erik@kryo.se \
--cc=jkosina@suse.cz \
--cc=konstantin@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lkp@intel.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=tglx@linutronix.de \
/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