[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tencent_312AB3C62E6755325FB3477910430DB08509@qq.com>
Date: Wed, 14 Sep 2022 10:58:01 +0800
From: Rong Tao <rtoax@...mail.com>
To: krzysztof.kozlowski@...aro.org
Cc: corbet@....net, erik@...o.se, jkosina@...e.cz,
konstantin@...uxfoundation.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux@...mhuis.info, lkp@...el.com,
ojeda@...nel.org, rdunlap@...radead.org, rongtao@...tc.cn,
rtoax@...mail.com, tglx@...utronix.de,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH v2] Documentation: process/submitting-patches: misspelling "mesages"
Fix spelling mistakes, "mesages" should be spelled "messages".
Signed-off-by: Rong Tao <rtoax@...mail.com>
Reviewed-by: Bagas Sanjaya <bagasdotme@...il.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