From: Christian Limpach <christian.limpach@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: "Magenheimer,
Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
xen-devel@lists.xensource.com
Subject: Re: xenstored.h
Date: Mon, 12 Sep 2005 21:11:15 +0100 [thread overview]
Message-ID: <3d8eece205091213113ec4999@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0509121528390.14856@cuia.boston.redhat.com>
On 9/12/05, Rik van Riel <riel@redhat.com> wrote:
> On Mon, 12 Sep 2005, Magenheimer, Dan (HP Labs Fort Collins) wrote:
>
> > Now that xenstore is in the mainline and xenstored.h is
> > part of the API to xenlinux, should xenstored.h be
> > moved into xen/include/public instead of being
> > mkbuildtree'd from tools/xenstore to drivers/xen/xenbus?
>
> Won't that make it impossible to build xenolinux kernels
> outside of the Xen tree - say, kernel RPMs ?
Yeah, you need to include those in your source RPMs - or have some
kind of xen-headers RPM which you'd then require to build kernels...
As Dan pointed out, the same applies for the other files in
xen/include/public...
christian
next prev parent reply other threads:[~2005-09-12 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 19:11 xenstored.h Magenheimer, Dan (HP Labs Fort Collins)
2005-09-12 19:28 ` xenstored.h Rik van Riel
2005-09-12 20:11 ` Christian Limpach [this message]
2005-09-12 23:52 ` xenstored.h Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2005-09-12 19:32 xenstored.h Magenheimer, Dan (HP Labs Fort Collins)
2005-09-12 23:57 xenstored.h Magenheimer, Dan (HP Labs Fort Collins)
2005-09-13 0:07 ` xenstored.h 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=3d8eece205091213113ec4999@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=dan.magenheimer@hp.com \
--cc=riel@redhat.com \
--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.