From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2 0/3] Better 'Force Unit Access' handling
Date: Wed, 11 May 2016 13:50:47 +0200 [thread overview]
Message-ID: <20160511115047.GC4524@noname.str.redhat.com> (raw)
In-Reply-To: <20160511013406.GC13488@ad.usersys.redhat.com>
Am 11.05.2016 um 03:34 hat Fam Zheng geschrieben:
> On Tue, 05/03 16:39, Eric Blake wrote:
> > I noticed some inconsistencies in FUA handling while working
> > with NBD, then Kevin pointed out that my initial attempt wasn't
> > quite right for iscsi which also had problems, so this has
> > expanded into a series rather than a single patch.
> >
> > I'm not sure if this is qemu-stable material at this point.
> >
> > Depends on Kevin's block-next branch.
> >
> > Also available as a tag at this location:
> > git fetch git://repo.or.cz/qemu/ericb.git nbd-fua-v2
> >
> > v1 was here:
> > https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg04674.html
> >
> > diffstat not worth posting, as the series is basically rewritten
> >
> > Eric Blake (3):
> > block: Make supported_write_flags a per-bds property
> > block: Honor BDRV_REQ_FUA during write_zeroes
> > nbd: Simplify client FUA handling
>
> Reviewed-by: Fam Zheng <famz@redhat.com>
Ah, sorry, forgot that you co-maintain this code now. So this is good
enough to merge the series. :-)
Thanks, applied to block-next.
Kevin
prev parent reply other threads:[~2016-05-11 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 22:39 [Qemu-devel] [PATCHv2 0/3] Better 'Force Unit Access' handling Eric Blake
2016-05-03 22:39 ` [Qemu-devel] [PATCHv2 1/3] block: Make supported_write_flags a per-bds property Eric Blake
2016-05-03 22:39 ` [Qemu-devel] [PATCHv2 2/3] block: Honor BDRV_REQ_FUA during write_zeroes Eric Blake
2016-05-03 22:39 ` [Qemu-devel] [PATCHv2 3/3] nbd: Simplify client FUA handling Eric Blake
2016-05-10 12:38 ` [Qemu-devel] [PATCHv2 0/3] Better 'Force Unit Access' handling Kevin Wolf
2016-05-11 13:30 ` Stefan Hajnoczi
2016-05-11 1:34 ` Fam Zheng
2016-05-11 11:50 ` Kevin Wolf [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=20160511115047.GC4524@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).