All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
	sw@weilnetz.de, mdroth@linux.vnet.ibm.com, armbru@redhat.com,
	pbonzini@redhat.com, mreitz@redhat.com, berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 8/9] vl: Switch qemu_uuid to QemuUUID
Date: Tue, 9 Aug 2016 23:13:52 -0400	[thread overview]
Message-ID: <20160810031352.GF5270@localhost.localdomain> (raw)
In-Reply-To: <20160810012856.GC11351@al.usersys.redhat.com>

On Wed, Aug 10, 2016 at 09:28:56AM +0800, Fam Zheng wrote:
> On Tue, 08/09 17:45, Jeff Cody wrote:
> > > diff --git a/util/uuid.c b/util/uuid.c
> > > index 80c89f0..5d8bc88 100644
> > > --- a/util/uuid.c
> > > +++ b/util/uuid.c
> > > @@ -61,18 +61,19 @@ char *qemu_uuid_unparse_strdup(const QemuUUID *uuid)
> > >                             uu[13], uu[14], uu[15]);
> > >  }
> > >  
> > > -int qemu_uuid_parse(const char *str, uint8_t *uuid)
> > > +int qemu_uuid_parse(QemuUUID *uuid, const char *str)
> > 
> > Wait, what's going on here?  Why switch the argument order away from the
> > libuuid order?
> 
> I don't see a strong reason to strictly follow libuuid, and thought it would be
> more nature to put the output first, but since it's a surprise to you, I can
> change it back.
>

I just wasn't sure if it was intentional (since it wasn't in the commit
message, and it was a difference from v2).  If you feel strongly about
changing the order, I can be OK with it too :)

  reply	other threads:[~2016-08-10  3:14 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
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 [this message]
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=20160810031352.GF5270@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=famz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.