From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, NeilBrown <neilb@suse.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Ming Lei <ming.lei@redhat.com>
Subject: Re: why does __split_and_process_bio use bio_clone_bioset?
Date: Sat, 16 Jun 2018 08:20:52 -0700 [thread overview]
Message-ID: <20180616152052.GA7934@infradead.org> (raw)
In-Reply-To: <20180615182631.GA6906@redhat.com>
On Fri, Jun 15, 2018 at 02:26:31PM -0400, Mike Snitzer wrote:
> Yes. Already queued, likely won't send to Linus until end of next week
> though.. unless you want it upstream sooner?
We only really need it as a baseline for the multi-page bio work, so
no real rush. I think I'll just include it with my pending cleanup
series with a big 'DO NOT APPLY, will be in 4.18-rc2' marker.
prev parent reply other threads:[~2018-06-16 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 8:19 why does __split_and_process_bio use bio_clone_bioset? Christoph Hellwig
2018-06-14 18:12 ` Mike Snitzer
2018-06-14 20:08 ` Mike Snitzer
2018-06-14 23:34 ` [dm-devel] " NeilBrown
2018-06-15 7:38 ` Christoph Hellwig
2018-06-15 18:26 ` Mike Snitzer
2018-06-16 15:20 ` Christoph Hellwig [this message]
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=20180616152052.GA7934@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=neilb@suse.com \
--cc=snitzer@redhat.com \
/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).