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

Re: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN

To: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
From: Chris Wright <chrisw@xxxxxxxxxx>
Date: Thu, 22 Dec 2005 08:29:10 -0800
Cc: xen-merge@xxxxxxxxxxxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Thu, 22 Dec 2005 16:30:33 +0000
List-id: xen-merge <xen-merge.lists.xensource.com>

* Jimi Xenidis (jimix@xxxxxxxxxxxxxx) wrote:
> Lets not forget CONFIG_PPC_XEN :)

After upstream dir rename shouldn't that be CONFIG_POWERPC_XEN? ;-) j/k

Are there good examples where CONFIG_XEN isn't sufficient?  It'd be nice
to eliminate the extra if possible.

thanks,
-chris

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

Follow-Ups:
- Re: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
  - From: Jimi Xenidis

References:
- RE: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
  - From: Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
  - From: Jan Beulich
- Re: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
  - From: Jimi Xenidis

Prev by Date: [Xen-merge] [PATCH] merge i386's segment.h
Next by Date: [Xen-merge] [PATCH] eliminate boot_params use
Previous by thread: Re: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
Next by thread: Re: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
Index(es):
- Date
- Thread

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