From: Christoph Hellwig <hch@infradead.org>
To: Ming Lin <mlin@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Kent Overstreet <kent.overstreet@gmail.com>,
Jens Axboe <axboe@kernel.dk>,
Dongsu Park <dongsu.park@profitbricks.com>,
Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH v3 2/4] md/raid10: make sync_request_write() call bio_copy_data()
Date: Fri, 24 Apr 2015 00:08:57 -0700 [thread overview]
Message-ID: <20150424070857.GB8648@infradead.org> (raw)
In-Reply-To: <1429830275-6792-3-git-send-email-mlin@kernel.org>
On Thu, Apr 23, 2015 at 04:04:33PM -0700, Ming Lin wrote:
> From: Kent Overstreet <kent.overstreet@gmail.com>
>
> Refactor sync_request_write() of md/raid10 to use bio_copy_data()
> instead of open coding bio_vec iterations.
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2015-04-24 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 23:04 [PATCH v3 0/4] preparation for block layer simplification Ming Lin
2015-04-23 23:04 ` [PATCH v3 1/4] block: refactor iov_count_pages() from bio_{copy,map}_user_iov() Ming Lin
2015-04-24 7:06 ` Christoph Hellwig
2015-04-23 23:04 ` [PATCH v3 2/4] md/raid10: make sync_request_write() call bio_copy_data() Ming Lin
2015-04-24 7:08 ` Christoph Hellwig [this message]
2015-04-23 23:04 ` [PATCH v3 3/4] fs: make _submit_bh consistent with generic bio chaining Ming Lin
2015-04-24 7:25 ` Christoph Hellwig
2015-04-23 23:04 ` [PATCH v3 4/4] PM: submit bio in a sane way in cases without bio_chain Ming Lin
2015-04-24 16:17 ` Christoph Hellwig
2015-04-25 6:23 ` Ming Lin
2015-04-30 17:34 ` Pavel Machek
2015-05-01 17:21 ` Christoph Hellwig
2015-05-04 14:14 ` Rafael J. Wysocki
[not found] ` <20150430164717.GA21211@amd>
2015-05-05 9:23 ` Pavel Machek
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=20150424070857.GB8648@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=dongsu.park@profitbricks.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mlin@kernel.org \
--cc=neilb@suse.de \
/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®