From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/3] build/tools: disable libvchan build on NetBSD
Date: Mon, 18 Jun 2012 11:46:29 +0100 [thread overview]
Message-ID: <4FDF0705.2050901@citrix.com> (raw)
In-Reply-To: <4FDEFE1E.20005@citrix.com>
Roger Pau Monne wrote:
> Ian Jackson wrote:
>> Christoph Egger writes ("Re: [Xen-devel] [PATCH 2/3] build/tools: disable libvchan build on NetBSD"):
>>> On 05/11/12 16:13, Roger Pau Monne wrote:
>>>> NetBSD doesn't have a gntdev, so libvchan is unable to build due to
>>>> the lack of the header files gntalloc.h.
>>> Acked-by: Christoph Egger<Christoph.Egger@amd.com>
>> Committed-by: Ian Jackson<ian.jackson@eu.citrix.com>
>
> I'm not sure this has been committed, could you please check it Ian?
Sorry for the fuss, I've found this one on staging.
Roger.
next prev parent reply other threads:[~2012-06-18 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 14:13 [PATCH 0/3] Minor fixes to the build system for NetBSD Roger Pau Monne
2012-05-11 14:13 ` [PATCH 1/3] autoconf/python_dev: pass include and library dir based on prefix Roger Pau Monne
2012-05-11 16:32 ` Ian Jackson
2012-05-14 9:51 ` Roger Pau Monne
2012-05-14 14:08 ` Ian Jackson
2012-05-11 14:13 ` [PATCH 2/3] build/tools: disable libvchan build on NetBSD Roger Pau Monne
2012-05-16 15:35 ` Christoph Egger
2012-06-08 15:22 ` Ian Jackson
2012-06-18 10:08 ` Roger Pau Monne
2012-06-18 10:38 ` Christoph Egger
2012-06-18 10:46 ` Roger Pau Monne [this message]
2012-05-11 14:13 ` [PATCH 3/3] autoconf: correctly parse *_INCLUDES and *_LIB env vars Roger Pau Monne
2012-06-08 15:22 ` Ian Jackson
2012-06-12 12:02 ` Roger Pau Monne
2012-06-26 16:32 ` Roger Pau Monne
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=4FDF0705.2050901@citrix.com \
--to=roger.pau@citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.