[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8AFC7968D54FB448A30D8F38F259C56223FE7ADB@TK5EX14MBXC114.redmond.corp.microsoft.com>
Date: Wed, 4 Aug 2010 04:25:40 +0000
From: Hank Janssen <hjanssen@...rosoft.com>
To: Greg KH <gregkh@...e.de>
CC: "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"'devel@...verdev.osuosl.org'" <devel@...verdev.osuosl.org>,
"'virtualization@...ts.osdl.org'" <virtualization@...ts.osdl.org>,
"Haiyang Zhang" <haiyangz@...rosoft.com>
Subject: RE: [PATCH 3/6] staging: hv: Fixed the value of the 64bit-hole
inside ring buffer
>>On Tue, Aug 03, 2010 at 05:31:57PM +0000, Hank Janssen wrote:
>> From: Haiyang Zhang <haiyangz@...rosoft.com>
>>
>> Fixed the value of the 64bit-hole inside ring buffer, this caused a problem on Hyper-V
>>when running checked Windows builds.
>
>What was the problem, and why would this fix it? Was it a bug in this code,
>by virtue that the code was incorrect in the client and the checked builds properly warned
>of this, or something else?
Checked builds of Windows are used internally and given to external system builders at times.
They are builds that for example that all elements in a structure follow the definition of that
Structure. The bug this fixed was for a field that we did not fill in at all (Because we do
Not use it on the Linux side), and the checked build of windows gives errors on it internally
to the Windows logs.
This fixes that error.
Thanks,
Hank.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists