[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240807071005.16329-1-shenxiaxi26@gmail.com>
Date: Wed, 7 Aug 2024 00:10:05 -0700
From: Xiaxi Shen <shenxiaxi26@...il.com>
To: kent.overstreet@...ux.dev,
corbet@....net
Cc: skhan@...uxfoundation.org,
javier.carrasco.cruz@...il.com,
shenxiaxi26@...il.com,
linux-bcachefs@...r.kernel.org (open list:BCACHEFS),
linux-doc@...r.kernel.org (open list:DOCUMENTATION),
linux-kernel@...r.kernel.org (open list)
Subject: [PATCH] Fix a spelling error in a doc of bcachefs
Signed-off-by: Xiaxi Shen <shenxiaxi26@...il.com>
---
Documentation/filesystems/bcachefs/CodingStyle.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/bcachefs/CodingStyle.rst b/Documentation/filesystems/bcachefs/CodingStyle.rst
index 0c45829a4899..01de555e21d8 100644
--- a/Documentation/filesystems/bcachefs/CodingStyle.rst
+++ b/Documentation/filesystems/bcachefs/CodingStyle.rst
@@ -175,7 +175,7 @@ errors in our thinking by running our code and seeing what happens. If your
time is being wasted because your tools are bad or too slow - don't accept it,
fix it.
-Put effort into your documentation, commmit messages, and code comments - but
+Put effort into your documentation, commit messages, and code comments - but
don't go overboard. A good commit message is wonderful - but if the information
was important enough to go in a commit message, ask yourself if it would be
even better as a code comment.
--
2.34.1
Powered by blists - more mailing lists