From: Roger Pau Monne <roger.pau@citrix.com>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] qemu-xen-trad: fix sys-queue.h usage on BSD systems
Date: Thu, 31 May 2012 15:13:01 +0100 [thread overview]
Message-ID: <4FC77C6D.5040704@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205311458070.26786@kaball-desktop>
Stefano Stabellini wrote:
> On Wed, 30 May 2012, Roger Pau Monne wrote:
>> BSD systems already have a sys/queue.h file, which has more macros
>> than the one Qemu uses, and some header files depend on having that
>> macros defined (sys/disk.h for example). Disable sys-queue.h on BSD
>> systems and include the native one.
>>
>> This is not a backport because the original patch is too dificult to
>> backport, it's commit 72cf2d4f0e181d0d3a3122e04129c58a95da713e.
>
> The upstream commit message states:
>
> "Problem: Our file sys-queue.h is a copy of the BSD file, but there are
> some additions and it's not entirely compatible. Because of that, there
> have been conflicts with system headers on BSD systems."
>
> Wouldn't this be a problem if we apply the simple patch below?
Doing a diff -bB shows that the Qemu version is just a stripped version
of the original NetBSD header, with many macros removed, but no new ones
added, so I think the patch is safe.
next prev parent reply other threads:[~2012-05-31 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 16:12 [PATCH] qemu-xen-trad: fix sys-queue.h usage on BSD systems Roger Pau Monne
2012-05-31 13:59 ` Stefano Stabellini
2012-05-31 14:13 ` Roger Pau Monne [this message]
2012-05-31 14:16 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2012-06-01 10:57 Roger Pau Monne
2012-06-01 10:59 ` Stefano Stabellini
2012-06-07 18:46 ` Ian Jackson
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=4FC77C6D.5040704@citrix.com \
--to=roger.pau@citrix.com \
--cc=Stefano.Stabellini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).