RE: [PATCH v1 4/6] vmbus: Switch to use new generic UUID API
From: Haiyang Zhang
Date: Wed Jul 19 2017 - 16:18:36 EST
> -----Original Message-----
> From: Andy Shevchenko [mailto:andriy.shevchenko@xxxxxxxxxxxxxxx]
> Sent: Wednesday, July 19, 2017 2:29 PM
> To: linux-acpi@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx;
> sparmaintainer@xxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxx; linux-
> wireless@xxxxxxxxxxxxxxx; linux-watchdog@xxxxxxxxxxxxxxx; linux-
> efi@xxxxxxxxxxxxxxx; Christoph Hellwig <hch@xxxxxx>; linux-
> kernel@xxxxxxxxxxxxxxx; Lukas Wunner <lukas@xxxxxxxxx>
> Cc: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>; KY Srinivasan
> <kys@xxxxxxxxxxxxx>; Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>; Stephen
> Hemminger <sthemmin@xxxxxxxxxxxxx>
> Subject: [PATCH v1 4/6] vmbus: Switch to use new generic UUID API
>
> @@ -118,8 +116,8 @@ enum hv_fcopy_op {
>
> struct hv_fcopy_hdr {
> __u32 operation;
> - uuid_le service_id0; /* currently unused */
> - uuid_le service_id1; /* currently unused */
> + __u8 service_id0[16]; /* currently unused */
> + __u8 service_id1[16]; /* currently unused */
> } __attribute__((packed));
Even user space may not have all guid_t operations, could you still
put guid_t here for consistency? This file is also used by our kernel
mode code.
Thanks,
- Haiyang