From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Rong Tao <rtoax@foxmail.com>, corbet@lwn.net
Cc: kernel test robot <lkp@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Erik Ekman <erik@kryo.se>, Jiri Kosina <jkosina@suse.cz>,
Miguel Ojeda <ojeda@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: process/submitting-patches: misspelling "mesages"
Date: Tue, 13 Sep 2022 20:40:03 +0700 [thread overview]
Message-ID: <7862b646-9214-3f0c-54d4-6183157f2c2a@gmail.com> (raw)
In-Reply-To: <tencent_6A928C02229619E8099167DD5CCAA8D8BF0A@qq.com>
On 9/13/22 12:11, Rong Tao wrote:
> Fix spelling mistakes, "mesages" should be spelled "messages".
>
Hmm... I guess this is [PATCH v2], right?
> -Backtraces in commit mesages
> -^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> +Backtraces in commit messages
> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
The diff looks OK, thanks.
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-09-13 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 5:11 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
2022-09-14 2:58 ` Rong Tao
2022-09-13 13:40 ` Bagas Sanjaya [this message]
2022-09-13 14:02 ` Re: [PATCH] " Rong Tao
-- strict thread matches above, loose matches on Subject: below --
2022-09-09 6:23 Rong Tao
2022-09-09 20:10 ` kernel test robot
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=7862b646-9214-3f0c-54d4-6183157f2c2a@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--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=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
all inboxes | Powered by JetHome®