From: Ming Lei <ming.lei@redhat.com>
To: Shaohua Li <shli@kernel.org>, linux-raid@vger.kernel.org
Cc: NeilBrown <neilb@suse.com>,
linux-block@vger.kernel.org, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@infradead.org>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH v2 0/3] md: three misc changes
Date: Fri, 14 Jul 2017 16:14:41 +0800 [thread overview]
Message-ID: <20170714081444.32645-1-ming.lei@redhat.com> (raw)
This 1st patch fixes one issue introduced in the following two
commits:
Fixes: f0250618361d(md: raid10: don't use bio's vec table to manage resync pages)
Fixes: 98d30c5812c3(md: raid1: don't use bio's vec table to manage resync pages)
The 2nd one initializes bvec table of bio via bio_add_page() after bio_reset().
The 3rd one moves the common definitation and helpers into raid1-10.c.
V2:
- fix 'page_idx' increasement in patch 1
- move raid1/raid10 common code to raid1-raid10.c, as suggested by Neil
Ming Lei (3):
md: remove 'idx' from 'struct resync_pages'
md: raid1/raid10: initialize bvec table via bio_add_page()
md: raid1-10: move raid1/raid10 common code into raid1-10.c
drivers/md/md.h | 54 ----------------------------------
drivers/md/raid1-10.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/md/raid1.c | 31 ++++----------------
drivers/md/raid10.c | 19 ++++--------
4 files changed, 93 insertions(+), 92 deletions(-)
create mode 100644 drivers/md/raid1-10.c
--
2.9.4
next reply other threads:[~2017-07-14 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 8:14 Ming Lei [this message]
2017-07-14 8:14 ` [PATCH v2 1/3] md: remove 'idx' from 'struct resync_pages' Ming Lei
2017-07-14 8:14 ` [PATCH v2 2/3] md: raid1/raid10: initialize bvec table via bio_add_page() Ming Lei
2017-07-14 8:14 ` [PATCH v2 3/3] md: raid1-10: move raid1/raid10 common code into raid1-10.c Ming Lei
2017-07-16 5:14 ` Coly Li
2017-07-17 0:15 ` Ming Lei
2017-07-16 22:40 ` NeilBrown
2017-07-17 16:41 ` [PATCH v2 0/3] md: three misc changes Shaohua 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=20170714081444.32645-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=shli@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;
as well as URLs for NNTP newsgroup(s).