[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW2PR2101MB1052AB02CB74E0D165409344D7C70@MW2PR2101MB1052.namprd21.prod.outlook.com>
Date: Fri, 3 Apr 2020 01:56:20 +0000
From: Michael Kelley <mikelley@...rosoft.com>
To: vkuznets <vkuznets@...hat.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Wei Liu <wei.liu@...nel.org>,
Tianyu Lan <Tianyu.Lan@...rosoft.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"Andrea Parri (Microsoft)" <parri.andrea@...il.com>
Subject: RE: [PATCH 4/5] Drivers: hv: make sure that 'struct
vmbus_channel_message_header' compiles correctly
From: Vitaly Kuznetsov <vkuznets@...hat.com> Sent: Wednesday, April 1, 2020 3:38 AM
>
> Strictly speaking, compiler is free to use something different from 'u32'
> for 'enum vmbus_channel_message_type' (e.g. char) but it doesn't happen in
> real life, just add a BUILD_BUG_ON() guardian.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
> ---
> drivers/hv/vmbus_drv.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Powered by blists - more mailing lists