From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: Re: [PATCH] fix build when CONFIG_COMPAT disabled
Date: Fri, 12 Jan 2007 07:49:22 +0000
Message-ID: <45A74B92.76E4.0078.0@novell.com>
References: <45A67470.76E4.0078.0@novell.com>
	<C1CC2B19.77F9%keir@xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C1CC2B19.77F9%keir@xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Cc: John Levon <levon@movementarian.org>
List-Id: xen-devel@lists.xenproject.org

>CONFIG_COMPAT isn't a real config option though. It's a function of the
>architecture we're building for. So we don't need ifdef CONFIG_COMPAT in any
>x86/64-specific code.

Okay, I didn't view it that way - I really thought that it wouldn't be bad to be
able to turn off optional features like HVM or COMPAT...

Jan