qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eric Blake <eblake@redhat.com>, Stefan Weil <sw@weilnetz.de>,
	qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
	mdroth@linux.vnet.ibm.com, mreitz@redhat.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/7] vdi: Use QEMU UUID API
Date: Fri, 5 Aug 2016 16:47:49 +0800	[thread overview]
Message-ID: <20160805084749.GC8458@ad.usersys.redhat.com> (raw)
In-Reply-To: <874m6z9160.fsf@dusky.pond.sub.org>

On Fri, 08/05 08:31, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
> 
> > On 08/04/2016 12:58 PM, Stefan Weil wrote:
> >> Hi,
> >> 
> >> On 08/02/16 11:18, Fam Zheng wrote:
> >>> The QEMU UUID api, including the data structure (qemu_uuid_t), is fully
> >>> compatible with libuuid.  Use it, and remove the unused code.
> >>>
> >>> Signed-off-by: Fam Zheng <famz@redhat.com>
> >>> ---
> >>>  block/vdi.c | 49 ++++++++++---------------------------------------
> >>>  1 file changed, 10 insertions(+), 39 deletions(-)
> >>>
> >
> >>> @@ -182,10 +153,10 @@ typedef struct {
> >>>      uint32_t block_extra;       /* unused here */
> >>>      uint32_t blocks_in_image;
> >>>      uint32_t blocks_allocated;
> >>> -    uuid_t uuid_image;
> >>> -    uuid_t uuid_last_snap;
> >>> -    uuid_t uuid_link;
> >>> -    uuid_t uuid_parent;
> >>> +    qemu_uuid_t uuid_image;
> >>> +    qemu_uuid_t uuid_last_snap;
> >>> +    qemu_uuid_t uuid_link;
> >>> +    qemu_uuid_t uuid_parent;
> >> 
> >> As far as I remember, _t should be avoided because that postfix is
> >> reserved by POSIX. Should we use qemu_uuid, or can we ignore POSIX
> >> because the type name uses the qemu_ prefix?
> >
> > Correct that POSIX reserved all _t (which is a bit broad, oh well), and
> > also correct that we can take the risk of using it anyways (but if POSIX
> > ever standardizes something, we get to keep both of our broken pieces).
> >
> >
> >> Either with qemu_uuid_t or with qemu_uuid:
> >
> > I thought our coding standard preferred QemuUUID or something similar in
> > camelcase, rather than lower case.
> 
> Correct.  It's ugly (in my opinion), but we should stick to it, so it's
> at least consistently ugly.
> 
> >                                     But now we are just painting a
> > bikeshed, so I won't strongly object.
> 
> I'd prefer QemuUUID.

Fair enough. If QEMUUUID wasn't so UNREADABLE, I'd have used it.

Will change to QemuUUID. It's a bit more acceptable to me.

Fam

  reply	other threads:[~2016-08-05  8:48 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
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 [this message]
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=20160805084749.GC8458@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@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).