From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
"open list:Block I/O path" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v7] block: Move BlockRequest type to io.c
Date: Tue, 24 May 2016 13:00:49 +0800 [thread overview]
Message-ID: <20160524050049.GI14601@ad.usersys.redhat.com> (raw)
In-Reply-To: <1463699150-19445-1-git-send-email-eblake@redhat.com>
On Thu, 05/19 17:05, Eric Blake wrote:
> I was thrown by the fact that the public type BlockRequest had
> an anonymous union, but no obvious discriminator. Turns out
> that the only client of the second branch of the union was code
> internal to io.c, now that commit 91c6e4b killed public
> multiwrite, so move it into io.c and improve the comments.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
Thanks, applied to my block branch:
https://github.com/famz/qemu/tree/block
prev parent reply other threads:[~2016-05-24 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 23:05 [Qemu-devel] [PATCH v7] block: Move BlockRequest type to io.c Eric Blake
2016-05-24 5:00 ` Fam Zheng [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=20160524050049.GI14601@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).