WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] new -xen.c files in sparse tree

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] new -xen.c files in sparse tree
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 08 Feb 2007 10:22:00 +0000
Delivery-date: Thu, 08 Feb 2007 02:18:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
What is the purpose of adding arch/i386/kernel/alternative-xen.c, when the
delta to native is a single line?

Even more funny - arch/i386/kernel/intel_cacheinfo-xen.c doesn't show any
difference to native...

Shouldn't we try to reduce the number of such files, to ease maintaining them?

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>