From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: [Qemu-devel] Re: [PATCH 5/6] qemu fixes
Date: Fri, 28 Nov 2008 12:34:54 +0100 [thread overview]
Message-ID: <492FD75E.9040900@siemens.com> (raw)
In-Reply-To: <200811281139.07092.Christoph.Egger@amd.com>
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?
Jan
--
Siemens AG, Corporate Technology, CT SE 2 ES-OS
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-11-28 11:34 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 ` Jan Kiszka [this message]
2008-11-28 11:56 ` [Qemu-devel] " Christoph Egger
2008-11-28 12:17 ` Jan Kiszka
2008-11-28 16:46 ` M. Warner Losh
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=492FD75E.9040900@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=blauwirbel@gmail.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 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.