From: aq <aquynh@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Xen Dev <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xs.h and xs_lib.h
Date: Tue, 14 Jun 2005 13:46:54 +0900 [thread overview]
Message-ID: <9cde8bff05061321467b982b1c@mail.gmail.com> (raw)
In-Reply-To: <1118709165.18549.5.camel@localhost.localdomain>
On 6/14/05, Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Mon, 2005-06-13 at 00:14 +0900, aq wrote:
> > On 6/12/05, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > > On Fri, 2005-06-10 at 03:32 -0500, aq wrote:
> > > > This patch moves declaration of xs_handle from xs.c to xs.h.
> > >
> > > No; why do this? It's opaque for a reason. Originally it was just an
> > > int, but Keir insisted it be an opaque structure. Exposing it binds us
> > > to the current structure again.
> > >
> > > > Besides,
> > > > it installs xs.h and xs_lib.h to /usr/include, and gets top Makefile
> > > > uninstalled them when cleaning up.
> > >
> > > xs_lib.h should not be installed in /usr/include!
> >
> > i see that, but where should we put this header?
>
> Once the daemon and library are built, it's not necessary for anything.
>
i installed xs_lib.h because xs.h includes it. now we need to remove
this and include xs_lib.h in other files as needed.
later i will send in another patch to fix this, and revert the problem
raised in last patch.
regards,
aq
next prev parent reply other threads:[~2005-06-14 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 8:32 [PATCH] xs.h and xs_lib.h aq
2005-06-10 8:31 ` Keir Fraser
2005-06-12 6:36 ` Rusty Russell
2005-06-12 15:14 ` aq
2005-06-14 0:32 ` Rusty Russell
2005-06-14 4:46 ` aq [this message]
2005-06-14 22:49 ` Rusty Russell
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=9cde8bff05061321467b982b1c@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=rusty@rustcorp.com.au \
--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.