[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <tencent_6A928C02229619E8099167DD5CCAA8D8BF0A@qq.com>
Date: Tue, 13 Sep 2022 13:11:09 +0800
From: Rong Tao <rtoax@...mail.com>
To: corbet@....net
Cc: Rong Tao <rtoax@...mail.com>, kernel test robot <lkp@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
Randy Dunlap <rdunlap@...radead.org>,
Thorsten Leemhuis <linux@...mhuis.info>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Erik Ekman <erik@...o.se>, Jiri Kosina <jkosina@...e.cz>,
Miguel Ojeda <ojeda@...nel.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] Documentation: process/submitting-patches: misspelling "mesages"
Fix spelling mistakes, "mesages" should be spelled "messages".
Signed-off-by: Rong Tao <rtoax@...mail.com>
Reported-by: kernel test robot <lkp@...el.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
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Backtraces help document the call chain leading to a problem. However,
not all backtraces are helpful. For example, early boot call chains are
--
2.31.1
Powered by blists - more mailing lists