From: Fam Zheng <famz@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] xenpv: Fix qemu_uuid compiling error
Date: Thu, 29 Sep 2016 11:38:11 +0800 [thread overview]
Message-ID: <20160929033811.GF6412@lemon> (raw)
In-Reply-To: <alpine.DEB.2.10.1609281703060.9519@sstabellini-ThinkPad-X260>
On Wed, 09/28 17:03, Stefano Stabellini wrote:
> On Tue, 27 Sep 2016, Eric Blake wrote:
> > On 09/27/2016 04:20 AM, Fam Zheng wrote:
> > > 9c5ce8db2 switched the type of qemu_uuid and this should have followed.
> > > Fix it.
> > >
> > > Signed-off-by: Fam Zheng <famz@redhat.com>
> > > ---
> > > hw/xenpv/xen_domainbuild.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Reviewed-by: Eric Blake <eblake@redhat.com>
>
> Acked-by: Stefano Stabellini <sstabellini@kernel.org>
Queued for next pull request, thanks.
Fam
prev parent reply other threads:[~2016-09-29 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 9:20 [PATCH] xenpv: Fix qemu_uuid compiling error Fam Zheng
2016-09-27 15:08 ` Eric Blake
2016-09-29 0:03 ` Stefano Stabellini
2016-09-29 3:38 ` 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=20160929033811.GF6412@lemon \
--to=famz@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.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).