From: Blue Swirl <blauwirbel@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Fix qemu_eventfd compile when !CONFIG_EVENTFD
Date: Tue, 23 Feb 2010 19:46:40 +0200 [thread overview]
Message-ID: <f43fc5581002230946q1014f58g5785aa7154ed422c@mail.gmail.com> (raw)
In-Reply-To: <1266916613-13238-1-git-send-email-pbonzini@redhat.com>
Thanks, applied.
On 2/23/10, Paolo Bonzini <pbonzini@redhat.com> wrote:
> From: Avi Kivity <avi@redhat.com>
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> osdep.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/osdep.c b/osdep.c
> index 3bab79a..4d39f2c 100644
> --- a/osdep.c
> +++ b/osdep.c
> @@ -293,9 +293,9 @@ ssize_t qemu_write_full(int fd, const void *buf, size_t count)
> */
> int qemu_eventfd(int fds[2])
> {
> +#ifdef CONFIG_EVENTFD
> int ret;
>
> -#ifdef CONFIG_EVENTFD
> ret = eventfd(0, 0);
> if (ret >= 0) {
> fds[0] = ret;
>
> --
> 1.6.6
>
>
>
>
prev parent reply other threads:[~2010-02-23 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 9:16 [Qemu-devel] [PATCH] Fix qemu_eventfd compile when !CONFIG_EVENTFD Paolo Bonzini
2010-02-23 17:46 ` Blue Swirl [this message]
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=f43fc5581002230946q1014f58g5785aa7154ed422c@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=avi@redhat.com \
--cc=pbonzini@redhat.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).