From: Kent Overstreet <kmo@daterainc.com>
To: Olof Johansson <olof@lixom.net>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Mason <chris.mason@fusionio.com>,
Mike Snitzer <snitzer@redhat.com>, NeilBrown <neilb@suse.de>
Subject: Re: [PATCH] block: Revert bio_clone() default behaviour
Date: Tue, 5 Nov 2013 21:07:45 -0800 [thread overview]
Message-ID: <20131106050745.GA17641@moria.home.lan> (raw)
In-Reply-To: <CAOesGMjiPuqqP4oxd8vmvpbu5JZb=Nru59p5zX5KydAarSp2Rw@mail.gmail.com>
On Tue, Nov 05, 2013 at 09:02:19PM -0800, Olof Johansson wrote:
> Hi,
>
> On Tue, Nov 5, 2013 at 7:48 PM, Kent Overstreet <kmo@daterainc.com> wrote:
>
> > Chris, Olaf, can you two in particular test this? I have tested the bounce
> > buffer code (and bcache), but Jens told me today there was an md bug that I
> > _still_ can't find any emails about so I'm not sure what to test for that.
>
> (I'm guessing you mean me and not some German person here. :-)
>
> What is this expected to apply on top of? It doesn't apply cleanly on
> the 20131105 -next tree which is where I had been seeing the issues.
Sorry - it's on top of Jens' for-3.13/core branch,
git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
next prev parent reply other threads:[~2013-11-06 5:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 3:48 [PATCH] block: Revert bio_clone() default behaviour Kent Overstreet
2013-11-06 5:02 ` Olof Johansson
2013-11-06 5:07 ` Kent Overstreet [this message]
2013-11-06 15:25 ` Olof Johansson
2013-11-06 16:11 ` Chris Mason
2013-11-06 20:02 ` Kent Overstreet
2013-11-06 20:22 ` Chris Mason
2013-11-06 20:36 ` Mike Snitzer
2013-11-06 20:49 ` Chris Mason
2013-11-06 20:57 ` [PATCH] " Kent Overstreet
2013-11-06 21:25 ` Chris Mason
2013-11-06 21:51 ` Kent Overstreet
2013-11-07 4:59 ` NeilBrown
2013-11-06 20:31 ` Mike Snitzer
2013-11-06 20:40 ` Kent Overstreet
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=20131106050745.GA17641@moria.home.lan \
--to=kmo@daterainc.com \
--cc=axboe@kernel.dk \
--cc=chris.mason@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.