Messages in this thread | | | From | Haiyang Zhang <> | Subject | RE: [PATCH v1 4/6] vmbus: Switch to use new generic UUID API | Date | Wed, 19 Jul 2017 20:18:24 +0000 |
| |
> -----Original Message----- > From: Andy Shevchenko [mailto:andriy.shevchenko@linux.intel.com] > Sent: Wednesday, July 19, 2017 2:29 PM > To: linux-acpi@vger.kernel.org; devel@linuxdriverproject.org; > sparmaintainer@unisys.com; devel@driverdev.osuosl.org; linux- > wireless@vger.kernel.org; linux-watchdog@vger.kernel.org; linux- > efi@vger.kernel.org; Christoph Hellwig <hch@lst.de>; linux- > kernel@vger.kernel.org; Lukas Wunner <lukas@wunner.de> > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>; KY Srinivasan > <kys@microsoft.com>; Haiyang Zhang <haiyangz@microsoft.com>; Stephen > Hemminger <sthemmin@microsoft.com> > 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
| |