From: "Jan Beulich" <jbeulich@novell.com>
Subject: Re: [PATCH] conditionalize PCI reassign code
Date: Fri, 17 Oct 2008 08:17:39 +0100
Message-ID: <48F85833.76E4.0078.0@novell.com>
References: <48F4BD46.76E4.0078.0@novell.com> <48F7FBE9.6030207@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <48F7FBE9.6030207@intel.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.fraser@eu.citrix.com>, Yu Zhao <yu.zhao@intel.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

>>> "Zhao, Yu" <yu.zhao@intel.com> 17.10.08 04:43 >>>
>There is build error (c/s 701) with this patch, please take a look.

This is why I always include

>> As usual, written and tested on 2.6.27 and made apply to the 2.6.18
>> tree without further testing.

I'm making a best effort attempt at getting things in proper state for =
that
tree, but time-wise can't afford full validation. But I always assumed =
that
if this appears in the real (not the staging) tree, it at least survived
building in Citrix' trees - is that not correct, Keir?

As you observed the build error - why don't you provide at least the
error the compiler generated? That might make it possible to provide a
fix quickly.

Jan