From: Fam Zheng <famz@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org, berrange@redhat.com, pbonzini@redhat.com,
kwolf@redhat.com, mreitz@redhat.com, mdroth@linux.vnet.ibm.com,
armbru@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/7] util: Add UUID API
Date: Mon, 8 Aug 2016 14:33:17 +0800 [thread overview]
Message-ID: <20160808063317.GA24378@al.usersys.redhat.com> (raw)
In-Reply-To: <78def4e2-aec9-d7c7-6e35-4a6c9da23057@weilnetz.de>
On Mon, 08/08 08:30, Stefan Weil wrote:
> Am 02.08.2016 um 11:18 schrieb Fam Zheng:
> [...]
> > +void qemu_uuid_generate(qemu_uuid_t out)
> > +{
> > + /* Version 4 UUID, RFC4122 4.4. */
> > + QEMU_BUILD_BUG_ON(sizeof(qemu_uuid_t) != 16);
> > + *((guint32 *)out + 0) = g_random_int();
> > + *((guint32 *)out + 1) = g_random_int();
> > + *((guint32 *)out + 2) = g_random_int();
> > + *((guint32 *)out + 3) = g_random_int();
>
> I suggest using uint32_t instead of guint32.
> Up to now, nearly all QEMU code uses the POSIX data types.
This is merely to keep consistent with the g_random_int() return type. If the
two types had any chance to vary (surely they don't), the uint32_t way would
look like this:
*((uint32_t *)out + 0) = (uint32_t)g_random_int();
So I think the current way is fine.
Fam
next prev parent reply other threads:[~2016-08-08 6:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 9:18 [Qemu-devel] [PATCH 0/7] UUID clean ups for 2.8 Fam Zheng
2016-08-02 9:18 ` [Qemu-devel] [PATCH 1/7] util: Add UUID API Fam Zheng
2016-08-02 19:45 ` Paolo Bonzini
2016-08-03 2:36 ` Fam Zheng
2016-08-03 4:19 ` Jeff Cody
2016-08-04 12:44 ` Paolo Bonzini
2016-08-04 12:54 ` Marc-André Lureau
2016-08-04 15:33 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2016-08-08 3:07 ` Fam Zheng
2016-08-08 5:53 ` Fam Zheng
2016-08-04 15:48 ` [Qemu-devel] " Daniel P. Berrange
2016-08-05 8:48 ` Fam Zheng
2016-08-08 6:30 ` Stefan Weil
2016-08-08 6:33 ` Fam Zheng [this message]
2016-08-08 7:10 ` Stefan Weil
2016-08-08 10:52 ` Markus Armbruster
2016-08-02 9:18 ` [Qemu-devel] [PATCH 2/7] vhdx: Use QEMU " Fam Zheng
2016-08-02 9:18 ` [Qemu-devel] [PATCH 3/7] vdi: " Fam Zheng
2016-08-04 18:58 ` Stefan Weil
2016-08-04 20:34 ` Eric Blake
2016-08-05 6:31 ` Markus Armbruster
2016-08-05 8:47 ` Fam Zheng
2016-08-02 9:18 ` [Qemu-devel] [PATCH 4/7] vpc: " Fam Zheng
2016-08-02 9:18 ` [Qemu-devel] [PATCH 5/7] crypto: Switch to " Fam Zheng
2016-08-02 9:18 ` [Qemu-devel] [PATCH 6/7] tests: No longer dependent on CONFIG_UUID Fam Zheng
2016-08-02 9:18 ` [Qemu-devel] [PATCH 7/7] configure: Remove detection code for UUID 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=20160808063317.GA24378@al.usersys.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@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).