[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH v3 8/9] vl: Switch qemu_uuid to QemuUUID
From: |
Jeff Cody |
Subject: |
Re: [Qemu-block] [PATCH v3 8/9] vl: Switch qemu_uuid to QemuUUID |
Date: |
Tue, 9 Aug 2016 23:13:52 -0400 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
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 :)
- Re: [Qemu-block] [Qemu-devel] [PATCH v3 1/9] util: Add UUID API, (continued)
- [Qemu-block] [PATCH v3 2/9] vhdx: Use QEMU UUID API, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 3/9] vdi: Use QEMU UUID API, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 4/9] vpc: Use QEMU UUID API, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 5/9] crypto: Switch to QEMU UUID API, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 6/9] tests: No longer dependent on CONFIG_UUID, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 7/9] configure: Remove detection code for UUID, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 8/9] vl: Switch qemu_uuid to QemuUUID, Fam Zheng, 2016/08/09
- [Qemu-block] [PATCH v3 9/9] tests: Add uuid tests, Fam Zheng, 2016/08/09