From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen Date: Wed, 18 May 2005 19:20:01 +0100 Message-ID: <3d8eece205051811206f1d4e7b@mail.gmail.com> References: <516F50407E01324991DD6D07B0531AD542CDA8@cacexc12.americas.cpqcorp.net> <20050517175807.GG27549@shell0.pdx.osdl.net> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20050517175807.GG27549@shell0.pdx.osdl.net> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Chris Wright Cc: "Magenheimer, Dan (HP Labs Fort Collins)" , xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org On 5/17/05, Chris Wright wrote: > * Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote: > > Where are xen-generic header files going to go? >=20 > Will include/xen/ work for you? If that's acceptable, then I think that any of arch/xen (without the arch specific subdirectories), xen (toplevel xen, how does it compare in significance/ubiquity to crypto, fs, ipc, net, security or sound?) or {kernel,mm,drivers/pci}/xen would seem just as reasonable and make more sense than drivers/xen... christian