From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>
Cc: Marcelo Tosatti <marcelo@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Jan Kiszka to maintain kvm-kmod
Date: Mon, 26 Oct 2009 11:02:33 +0200 [thread overview]
Message-ID: <4AE565A9.4000907@redhat.com> (raw)
I am pleased to announce that Jan Kiszka has agreed to maintain
kvm-kmod.git, the backporting kit that allows running modern kvm code on
older kernels. Jan will release kvm-kmod-2.6.x.y packages and
kvm-kmod-2.6.x-rcy packages, while Marcelo and I will (with Jan's help)
release kvm-kmod-devel-xx. Many thanks to Jan for taking on this task.
As there are now many different sources of kvm kernel modules to choose
from, I wrote up a page that describes the various releases and what
they are suited for. This can be found in
http://www.linux-kvm.org/page/Getting_the_kvm_kernel_modules.
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2009-10-26 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 9:02 Avi Kivity [this message]
2009-10-26 17:51 ` Jan Kiszka to maintain kvm-kmod Jan Kiszka
2009-10-27 10:43 ` Avi Kivity
2009-10-27 11:20 ` Jan Kiszka
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=4AE565A9.4000907@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=marcelo@redhat.com \
/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