From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen Date: Wed, 18 May 2005 12:15:16 +0200 Message-ID: <20050518101515.GA22028@snarc.org> References: <516F50407E01324991DD6D07B0531AD542CDB3@cacexc12.americas.cpqcorp.net> <20050517181435.GH27549@shell0.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20050517181435.GH27549@shell0.pdx.osdl.net> 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 Tue, May 17, 2005 at 11:14:35AM -0700, Chris Wright wrote: > [snip] So let's recap: xen arch code in arch/$(ARCH)/mach-xen/ xen generic code in drivers/xen/core/ xen arch includes in include/asm-$(ARCH)/mach-xen/ xen generic includes in include/asm-xen/ Now for arch that don't use mach-XX syntax we can probably make a xen directory instead of a mach-xen directory, but I'ld rather go with something consistant. As well we can probably host a public tree in cambridge for anybody interested in the files reorganisation. Any others thought, comments ? -- Vincent Hanquez