All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] avoid name clashes due to LIST_* macros
Date: Wed, 06 Feb 2008 13:14:43 -0600	[thread overview]
Message-ID: <47AA0723.7050701@codemonkey.ws> (raw)
In-Reply-To: <18328.31569.260208.382120@mariner.uk.xensource.com>

Ian Jackson wrote:
> qemu's audio subdirectory contains a copy of BSD's sys-queue.h, which
> defines a bunch of LIST_ macros.  This makes it difficult to build a
> program made partly out of qemu and partly out of the Linux kernel[1],
> since Linux has a different set of LIST_ macros.  It might also cause
> trouble when mixing with BSD-derived code.
>   

That doesn't seem like a very good justification.  If you're mixing QEMU 
code with other code, it's easier for you to maintain these merge 
conflict fixes as normal QEMU developers would have no idea what it 
wasn't okay to just use LIST_xxx

Regards,

Anthony Liguori

> Under the circumstances it's probably best to rename the versions in
> qemu.  The attached patch does this.
>
> [1] You might well ask why anyone would want to do this.  In Xen we
> are moving our emulation of IO devices from processes which run on the
> host into a dedicated VM (one per actual VM) which we call a `stub
> domain'.  This dedicated VM runs a very cut-down `operating system'
> which uses some code from Linux.
>
> Regards,
> Ian.
>
>   

  parent reply	other threads:[~2008-02-06 19:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 11:49 [Qemu-devel] [PATCH] avoid name clashes due to LIST_* macros Ian Jackson
2008-02-06 17:12 ` [Qemu-devel] " Ian Jackson
2008-02-06 19:14 ` Anthony Liguori [this message]
2008-02-07 10:23   ` [Qemu-devel] " Ian Jackson
2008-02-07 12:49     ` Johannes Schindelin
2008-02-07 12:52       ` Ian Jackson
2008-02-07 19:42         ` malc

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=47AA0723.7050701@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.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.