From: Christian Limpach <christian.limpach@gmail.com>
To: Chris Wright <chrisw@osdl.org>
Cc: "Magenheimer,
Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen
Date: Wed, 18 May 2005 19:20:01 +0100 [thread overview]
Message-ID: <3d8eece205051811206f1d4e7b@mail.gmail.com> (raw)
In-Reply-To: <20050517175807.GG27549@shell0.pdx.osdl.net>
On 5/17/05, Chris Wright <chrisw@osdl.org> wrote:
> * Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote:
> > Where are xen-generic header files going to go?
>
> 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
next prev parent reply other threads:[~2005-05-18 18:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 17:25 linux/arch/xen/i386 or linux/arch/i386/xen Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 17:58 ` Chris Wright
2005-05-18 18:20 ` Christian Limpach [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 17:18 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-19 18:55 ` Chris Wright
2005-05-18 19:21 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 17:00 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 17:17 ` Chris Wright
2005-05-18 18:35 ` Zachary Amsden
2005-05-18 15:09 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 16:47 ` Chris Wright
2005-05-18 19:00 ` Vincent Hanquez
2005-05-18 19:48 ` Zachary Amsden
2005-05-18 20:31 ` Vincent Hanquez
2005-05-17 19:05 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 18:09 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 18:14 ` Chris Wright
2005-05-18 10:15 ` Vincent Hanquez
2005-05-18 16:53 ` Chris Wright
2005-05-18 18:56 ` Vincent Hanquez
2005-05-16 22:42 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 22:50 ` Mark Williamson
2005-05-16 23:22 ` Chris Wright
2005-05-16 21:37 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 22:21 ` Mark Williamson
2005-05-16 17:36 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 18:07 ` Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d8eece205051811206f1d4e7b@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=chrisw@osdl.org \
--cc=dan.magenheimer@hp.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.