From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, Christoph.Egger@amd.com
Cc: blauwirbel@gmail.com, jan.kiszka@siemens.com
Subject: Re: [Qemu-devel] Re: [PATCH 5/6] qemu fixes
Date: Fri, 28 Nov 2008 09:46:04 -0700 (MST) [thread overview]
Message-ID: <20081128.094604.420505779.imp@bsdimp.com> (raw)
In-Reply-To: <200811281256.54759.Christoph.Egger@amd.com>
In message: <200811281256.54759.Christoph.Egger@amd.com>
Christoph Egger <Christoph.Egger@amd.com> writes:
: On Friday 28 November 2008 12:34:54 Jan Kiszka wrote:
: > Christoph Egger wrote:
: > > Hi,
: > >
: > > This is a series of four patches which improve support
: > > for qemu on NetBSD.
: > >
: > > sys-queue.h defines _SYS_QUEUE_H_ which is also defined by
: > > the <sys/queue.h> system header. <sys/disk.h> uses SLIST_ENTRY
: > > on NetBSD, which doesn't exist in sys-queue.h. Therefore,
: > > include <sys/queue.h> before including sys-queue.h.
: >
: > Does this patch (which my mail client unfortunately refuses to cite...)
: > take into account that we now have TAILQ_FOREACH_SAFE which NetBSD may
: > lack?
:
: Yes, NetBSD has it:
:
: #define TAILQ_FOREACH_SAFE(var, head, field, next) \
: for ((var) = ((head)->tqh_first); \
: (var) != NULL && ((next) = TAILQ_NEXT(var, field), 1); \
: (var) = (next))
:
: Another option to this patch would be:
:
: Renaming _SYS_QUEUE_H_ to QEMU_SYS_QUEUE_H_
: at least allows to include both sys-queue.h and <sys/queue.h>.
That would be the better option, because _XXX is reserved for the
compiler/library/toolchain, not for the application...
Warner
next prev parent reply other threads:[~2008-11-28 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 10:39 [Qemu-devel] [PATCH 5/6] qemu fixes Christoph Egger
2008-11-28 11:34 ` [Qemu-devel] " Jan Kiszka
2008-11-28 11:56 ` Christoph Egger
2008-11-28 12:17 ` Jan Kiszka
2008-11-28 16:46 ` M. Warner Losh [this message]
2008-12-05 18:00 ` Blue Swirl
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=20081128.094604.420505779.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=Christoph.Egger@amd.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--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 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).