de...@linuxdriverproject.org;
> > o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com; Nick Meier
> > Subject: Re: [PATCH 4/9] Correcting truncation error for constant
> > HV_CRASH_CTL_CRASH_NOTIFY
> >
> > On Tue, Mar 17, 2015 at 05:41:56PM -0700, K. Y. Srinivasan wr
eier
> Subject: Re: [PATCH 4/9] Correcting truncation error for constant
> HV_CRASH_CTL_CRASH_NOTIFY
>
> On Tue, Mar 17, 2015 at 05:41:56PM -0700, K. Y. Srinivasan wrote:
> > From: Nick Meier
> >
> > HV_CRASH_CTL_CRASH_NOTIFY is a 64 bit number. Depending on the
>
On Tue, Mar 17, 2015 at 05:41:56PM -0700, K. Y. Srinivasan wrote:
> From: Nick Meier
>
> HV_CRASH_CTL_CRASH_NOTIFY is a 64 bit number. Depending on the usage context,
> the value may be truncated. This patch is in response from the following
> email from Intel:
"from Intel:" is really vague, pl
On Tue, Mar 17, 2015 at 05:41:56PM -0700, K. Y. Srinivasan wrote:
> From: Nick Meier
>
> HV_CRASH_CTL_CRASH_NOTIFY is a 64 bit number. Depending on the usage context,
> the value may be truncated. This patch is in response from the following
> email from Intel:
Subject should have "hv:" at the
From: Nick Meier
HV_CRASH_CTL_CRASH_NOTIFY is a 64 bit number. Depending on the usage context,
the value may be truncated. This patch is in response from the following
email from Intel:
[char-misc:char-misc-testing 25/45] drivers/hv/vmbus_drv.c:67:9: sparse:
constant 0x80
