linux-kernel - Re: [PATCH] Fix a spelling error in a doc of bcachefs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2dfa76a7-eeae-4b05-bfcd-684ae7ade963@linuxfoundation.org>
Date: Wed, 7 Aug 2024 09:42:12 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: Xiaxi Shen <shenxiaxi26@...il.com>, kent.overstreet@...ux.dev,
 corbet@....net
Cc: javier.carrasco.cruz@...il.com,
 "open list:BCACHEFS" <linux-bcachefs@...r.kernel.org>,
 "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
 open list <linux-kernel@...r.kernel.org>,
 Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] Fix a spelling error in a doc of bcachefs

On 8/7/24 01:10, Xiaxi Shen wrote:

Missing commit message --

> 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.

thanks,
-- Shuah