From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC, PATCH] Host AIO support detection, OpenBSD host support
Date: Tue, 12 Aug 2008 14:46:53 -0500 [thread overview]
Message-ID: <48A1E8AD.9040501@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580808121145u483ef7b8l6cb86165d259cf93@mail.gmail.com>
Blue Swirl wrote:
> Here are two patches, loosely based on patches in OpenBSD ports system
> that enable compiling Qemu. The first patch makes AIO use conditional
> on host AIO support. The second one adjusts various include files etc.
>
> I'd like to commit both of these, is that OK?
>
The first patch is fine but the second patch has some bogus things in
it. For instance:
>
> Index: qemu/configure
> ===================================================================
> --- qemu.orig/configure 2008-08-12 17:12:15.000000000 +0000
> +++ qemu/configure 2008-08-12 17:33:36.000000000 +0000
> @@ -150,6 +150,7 @@
> @@ -1076,6 +1081,14 @@
> echo "#define HAVE_BYTESWAP_H 1" >> $config_h
> fi
> fi
> +
> +if [ "$openbsd" = "yes" ] ; then
> + echo "#define ENOTSUP 4096" >> $config_h
> + echo "#define qemu_siginfo siginfo_t" >> $config_h
> +else
> + echo "#define qemu_siginfo struct siginfo" >> $config_h
> +fi
But qemu_siginfo isn't actually used anywhere. That's just one example,
the patch seems to have a lot of things like this in it.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-08-12 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 18:45 [Qemu-devel] [RFC, PATCH] Host AIO support detection, OpenBSD host support Blue Swirl
2008-08-12 19:46 ` Anthony Liguori [this message]
2008-08-12 19:56 ` Todd T. Fries
2008-08-12 20:08 ` Anthony Liguori
2008-08-13 16:53 ` Blue Swirl
2008-08-13 16:48 ` Blue Swirl
2008-08-13 17:50 ` Anthony Liguori
2008-08-13 21:48 ` malc
2008-08-15 20:05 ` Blue Swirl
2008-08-15 20:29 ` Todd T. Fries
2008-08-16 16:26 ` malc
2008-08-16 16:36 ` Blue Swirl
2008-08-17 20:44 ` malc
2008-08-16 9:33 ` Blue Swirl
2008-08-12 21:07 ` Samuel Thibault
2008-08-12 21:17 ` Samuel Thibault
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=48A1E8AD.9040501@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 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).