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: Various compat fixes for older kernels
Date: Tue, 26 May 2009 10:49:35 +0300 [thread overview]
Message-ID: <4A1B9F0F.6050102@redhat.com> (raw)
In-Reply-To: <4A1A4377.7090903@web.de>
Jan Kiszka wrote:
> Various fixes that were required to build against a 2.6.18 kernel, but
> some affect newer kernels, too:
>
>
> - replacements for uaccess.h and relay.h
> - flush_work compat wrapper
> - fix msi_enabled hack
> - hack eventfd.c for INIT_WORK
>
Please split into separate patches.
> - move phys_addr_t and true/false definitions as headers require it
> earlier
> - add MSR_K7_HWCR definition
>
>
I had these two already, but not pushed. Maybe I need to have a script
push my master branch somewhere, so you don't duplicate my work needlessly.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-26 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 7:06 [PATCH] kvm-kmod: Various compat fixes for older kernels Jan Kiszka
2009-05-26 7:49 ` Avi Kivity [this message]
2009-05-26 8:26 ` Amit Shah
2009-05-26 9:01 ` Jan Kiszka
2009-05-26 9:11 ` Avi Kivity
2009-05-26 9:22 ` Jan Kiszka
2009-05-26 9:30 ` Avi Kivity
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=4A1B9F0F.6050102@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