From: Coly Li <colyli@suse.de>
To: axboe@kernel.dk
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
Jilin Yuan <yuanjilin@cdjrlc.com>, Coly Li <colyli@suse.de>
Subject: [PATCH 4/5] bcache:: fix repeated words in comments
Date: Tue, 20 Sep 2022 00:16:46 +0800 [thread overview]
Message-ID: <20220919161647.81238-5-colyli@suse.de> (raw)
In-Reply-To: <20220919161647.81238-1-colyli@suse.de>
From: Jilin Yuan <yuanjilin@cdjrlc.com>
Delete the redundant word 'we'.
Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
Signed-off-by: Coly Li <colyli@suse.de>
---
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.35.3
next prev parent reply other threads:[~2022-09-19 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 16:16 [PATCH 0/5] bcache patches for Linux v6.1 Coly Li
2022-09-19 16:16 ` [PATCH 1/5] bcache: remove unnecessary flush_workqueue Coly Li
2022-09-19 16:16 ` [PATCH 2/5] bcache: remove unused bch_mark_cache_readahead function def in stats.h Coly Li
2022-09-19 16:16 ` [PATCH 3/5] bcache: bset: Fix comment typos Coly Li
2022-09-19 16:16 ` Coly Li [this message]
2022-09-19 16:16 ` [PATCH 5/5] bcache: fix set_at_max_writeback_rate() for multiple attached devices Coly Li
2022-09-19 17:12 ` [PATCH 0/5] bcache patches for Linux v6.1 Jens Axboe
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=20220919161647.81238-5-colyli@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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