From: Coly Li <colyli@suse.de>
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcache:: fix repeated words in comments
Date: Wed, 31 Aug 2022 23:12:06 +0800 [thread overview]
Message-ID: <A39949D5-FEED-4A59-8BE5-9D90BE63521D@suse.de> (raw)
In-Reply-To: <20220830153026.16948-1-yuanjilin@cdjrlc.com>
> 2022年8月30日 23:30，Jilin Yuan <yuanjilin@cdjrlc.com> 写道：
>
> Delete the redundant word 'we'.
>
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
Added to my for-next queue. Thanks.
Coly Li
> ---
> drivers/md/bcache/bcache.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/md/bcache/bcache.h b/drivers/md/bcache/bcache.h
> index 2acda9cea0f9..aebb7ef10e63 100644
> --- a/drivers/md/bcache/bcache.h
> +++ b/drivers/md/bcache/bcache.h
> @@ -107,7 +107,7 @@
> *
> * BTREE NODES:
> *
> - * Our unit of allocation is a bucket, and we we can't arbitrarily allocate and
> + * Our unit of allocation is a bucket, and we can't arbitrarily allocate and
> * free smaller than a bucket - so, that's how big our btree nodes are.
> *
> * (If buckets are really big we'll only use part of the bucket for a btree node
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-08-31 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 15:30 [PATCH] bcache:: fix repeated words in comments Jilin Yuan
2022-08-31 15:12 ` Coly Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-18 9:45 [PATCH] bcache: " Jilin Yuan
2022-09-18 11:10 ` Coly Li
2022-09-18 11:14 ` Coly Li
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=A39949D5-FEED-4A59-8BE5-9D90BE63521D@suse.de \
--to=colyli@suse.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuanjilin@cdjrlc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).