From: Fam Zheng <famz@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, mdroth@linux.vnet.ibm.com,
qemu-block@nongnu.org, sw@weilnetz.de, armbru@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/9] util: Add UUID API
Date: Wed, 10 Aug 2016 09:25:10 +0800 [thread overview]
Message-ID: <20160810012510.GB11351@al.usersys.redhat.com> (raw)
In-Reply-To: <20160809194644.GO24882@localhost.localdomain>
On Tue, 08/09 15:46, Jeff Cody wrote:
> So the short of it: I think this new function should be explicitly called
> something like "qemu_uuid_bswap()", and do blind bswaps. That makes it a
> drop in replacement for VDI.
Right, I should make it bswap.
Fam
next prev parent reply other threads:[~2016-08-10 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 6:49 [Qemu-devel] [PATCH v3 0/9] UUID clean ups for 2.8 Fam Zheng
2016-08-09 6:49 ` [Qemu-devel] [PATCH v3 1/9] util: Add UUID API Fam Zheng
2016-08-09 19:46 ` Jeff Cody
2016-08-10 1:25 ` Fam Zheng [this message]
2016-08-09 21:45 ` Jeff Cody
2016-08-10 10:55 ` Richard Henderson
2016-08-11 4:33 ` Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 2/9] vhdx: Use QEMU " Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 3/9] vdi: " Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 4/9] vpc: " Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 5/9] crypto: Switch to " Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 6/9] tests: No longer dependent on CONFIG_UUID Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 7/9] configure: Remove detection code for UUID Fam Zheng
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 8/9] vl: Switch qemu_uuid to QemuUUID Fam Zheng
2016-08-09 21:45 ` Jeff Cody
2016-08-10 1:28 ` Fam Zheng
2016-08-10 3:13 ` Jeff Cody
2016-08-09 6:50 ` [Qemu-devel] [PATCH v3 9/9] tests: Add uuid tests Fam Zheng
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=20160810012510.GB11351@al.usersys.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).