From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm-kmod: x86: Define CONFIG_HAVE_KVM_EVENTFD when missing
Date: Sun, 24 May 2009 11:23:50 +0300 [thread overview]
Message-ID: <4A190416.5020501@redhat.com> (raw)
In-Reply-To: <4A17052E.9030302@web.de>
Jan Kiszka wrote:
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> x86/external-module-compat.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/x86/external-module-compat.h b/x86/external-module-compat.h
> index a9476ff..d74aaaa 100644
> --- a/x86/external-module-compat.h
> +++ b/x86/external-module-compat.h
> @@ -531,3 +531,7 @@ typedef u64 phys_addr_t;
> #ifndef CONFIG_HAVE_KVM_IRQCHIP
> #define CONFIG_HAVE_KVM_IRQCHIP 1
> #endif
> +
> +#ifndef CONFIG_HAVE_KVM_EVENTFD
> +#define CONFIG_HAVE_KVM_EVENTFD 1
> +#endif
>
I already have this, just forgot to push. Sorry.
(a good thing anyway since I forgot the #ifndef)
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-05-24 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 20:03 [PATCH] kvm-kmod: x86: Define CONFIG_HAVE_KVM_EVENTFD when missing Jan Kiszka
2009-05-24 8:23 ` Avi Kivity [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=4A190416.5020501@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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