From: Ming Lei <ming.lei@canonical.com>
To: Jens Axboe <axboe@kernel.dk>, linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Anton Altaparmakov <anton@tuxera.com>,
Ming Lei <ming.lei@canonical.com>
Subject: [PATCH 2/4] block: make 'struct bvec_iter' not depend on CONFIG_BLOCK
Date: Tue, 8 Mar 2016 19:29:44 +0800 [thread overview]
Message-ID: <1457436586-26833-3-git-send-email-ming.lei@canonical.com> (raw)
In-Reply-To: <1457436586-26833-1-git-send-email-ming.lei@canonical.com>
So that we can use bvec iterator to implement iterate_bvec(): lib/iov_iter.c.
Signed-off-by: Ming Lei <ming.lei@canonical.com>
---
include/linux/blk_types.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
index 86a38ea..fd8527b 100644
--- a/include/linux/blk_types.h
+++ b/include/linux/blk_types.h
@@ -26,8 +26,6 @@ struct bio_vec {
unsigned int bv_offset;
};
-#ifdef CONFIG_BLOCK
-
struct bvec_iter {
sector_t bi_sector; /* device address in 512 byte
sectors */
@@ -39,6 +37,8 @@ struct bvec_iter {
current bvec */
};
+#ifdef CONFIG_BLOCK
+
/*
* main unit of I/O for the block layer and lower layers (ie drivers and
* stacking drivers)
--
1.9.1
next prev parent reply other threads:[~2016-03-08 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 11:29 block & iov_iter: use bvec iterator to implement iterate_bvec() Ming Lei
2016-03-08 11:29 ` [PATCH 1/4] block: move bvec iterator into include/linux/bvec_iter.h Ming Lei
2016-03-08 11:29 ` Ming Lei [this message]
2016-03-08 11:29 ` [PATCH 3/4] block: mark 1st parameter of bvec_iter_advance as const Ming Lei
2016-03-08 11:29 ` [PATCH 4/4] iov_iter: use bvec iterator to implement iterate_bvec() Ming Lei
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=1457436586-26833-3-git-send-email-ming.lei@canonical.com \
--to=ming.lei@canonical.com \
--cc=anton@tuxera.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®