From: Gioh Kim <gi-oh.kim@profitbricks.com>
To: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Cc: Gioh Kim <gi-oh.kim@profitbricks.com>
Subject: [RFC] replace comments for bvl_vec with bio_vec
Date: Fri, 15 Jun 2018 13:15:54 +0200 [thread overview]
Message-ID: <20180615111554.14005-1-gi-oh.kim@profitbricks.com> (raw)
I think bvl_vec means bio_vec_list that was replaced with bio_vec
long time ago. If I am correct, I think some comments for blk_vec
need to be replaced with bio_vec.
Signed-off-by: Gioh Kim <gi-oh.kim@profitbricks.com>
---
include/linux/blk_types.h | 2 +-
include/linux/bvec.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
index 3c4f390aea4b..a39dc0a665b9 100644
--- a/include/linux/blk_types.h
+++ b/include/linux/blk_types.h
@@ -196,7 +196,7 @@ struct bio {
* Everything starting with bi_max_vecs will be preserved by bio_reset()
*/
- unsigned short bi_max_vecs; /* max bvl_vecs we can hold */
+ unsigned short bi_max_vecs; /* max bio_vecs we can hold */
atomic_t __bi_cnt; /* pin count */
diff --git a/include/linux/bvec.h b/include/linux/bvec.h
index fe7a22dd133b..6023dc9e6f79 100644
--- a/include/linux/bvec.h
+++ b/include/linux/bvec.h
@@ -38,7 +38,7 @@ struct bvec_iter {
sectors */
unsigned int bi_size; /* residual I/O count */
- unsigned int bi_idx; /* current index into bvl_vec */
+ unsigned int bi_idx; /* current index into bio_vec */
unsigned int bi_done; /* number of bytes completed */
--
2.14.1
reply other threads:[~2018-06-15 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180615111554.14005-1-gi-oh.kim@profitbricks.com \
--to=gi-oh.kim@profitbricks.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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®