[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 08 Feb 2007 15:30:29 +0000
  • Delivery-date: Thu, 08 Feb 2007 07:33:56 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdLlhAPTtQVzreJEduwPwAX8io7RQ==
  • Thread-topic: [Xen-devel] new -xen.c files in sparse tree

Empty files can certainly be removed. Where there's any diff at all, it's a
matter of taste whether we have separate files or ifdef XEN.

 -- Keir

On 8/2/07 10:22, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> 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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.