From: Miaohe Lin <linmiaohe@huawei.com>
To: <axboe@kernel.dk>, <tj@kernel.org>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linmiaohe@huawei.com>
Subject: [PATCH] block: Fix various comments
Date: Sat, 5 Sep 2020 05:41:39 -0400 [thread overview]
Message-ID: <20200905094139.3119-1-linmiaohe@huawei.com> (raw)
Fix various comments including wrong function names, global variable name
and so on.
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
---
block/bio.c | 2 +-
block/blk-cgroup.c | 2 +-
block/blk-mq.c | 4 ++--
block/blk-throttle.c | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/block/bio.c b/block/bio.c
index a323a5446221..8c16a6744c72 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -174,7 +174,7 @@ struct bio_vec *bvec_alloc(gfp_t gfp_mask, int nr, unsigned long *idx,
struct bio_vec *bvl;
/*
- * see comment near bvec_array define!
+ * see comment near bvec_slabs define!
*/
switch (nr) {
case 1:
diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
index c195365c9817..58c57ada3b79 100644
--- a/block/blk-cgroup.c
+++ b/block/blk-cgroup.c
@@ -1816,7 +1816,7 @@ EXPORT_SYMBOL_GPL(bio_associate_blkg_from_css);
* @bio: target bio
*
* Associate @bio with the blkg found from the bio's css and request_queue.
- * If one is not found, bio_lookup_blkg() creates the blkg. If a blkg is
+ * If one is not found, blkg_lookup_create() creates the blkg. If a blkg is
* already associated, the css is reused and association redone as the
* request_queue may have changed.
*/
diff --git a/block/blk-mq.c b/block/blk-mq.c
index d089825f9cd1..a6e0a360b5f1 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -1650,7 +1650,7 @@ void blk_mq_run_hw_queue(struct blk_mq_hw_ctx *hctx, bool async)
/*
* When queue is quiesced, we may be switching io scheduler, or
* updating nr_hw_queues, or other things, and we can't run queue
- * any more, even __blk_mq_hctx_has_pending() can't be called safely.
+ * any more, even blk_mq_hctx_has_pending() can't be called safely.
*
* And queue will be rerun in blk_mq_unquiesce_queue() if it is
* quiesced.
@@ -1666,7 +1666,7 @@ void blk_mq_run_hw_queue(struct blk_mq_hw_ctx *hctx, bool async)
EXPORT_SYMBOL(blk_mq_run_hw_queue);
/**
- * blk_mq_run_hw_queue - Run all hardware queues in a request queue.
+ * blk_mq_run_hw_queues - Run all hardware queues in a request queue.
* @q: Pointer to the request queue to run.
* @async: If we want to run the queue asynchronously.
*/
diff --git a/block/blk-throttle.c b/block/blk-throttle.c
index fee3325edf27..207c9a477165 100644
--- a/block/blk-throttle.c
+++ b/block/blk-throttle.c
@@ -182,7 +182,7 @@ struct throtl_grp {
struct blkg_rwstat stat_ios;
};
-/* We measure latency for request size from <= 4k to >= 1M */
+/* We measure latency for request size from >= 4k to <= 1M */
#define LATENCY_BUCKET_SIZE 9
struct latency_bucket {
--
2.19.1
next reply other threads:[~2020-09-05 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 9:41 Miaohe Lin [this message]
2020-09-24 13:12 linmiaohe
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=20200905094139.3119-1-linmiaohe@huawei.com \
--to=linmiaohe@huawei.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®