From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] qemu-kvm: Sort out upstream merge regressions
Date: Wed, 20 Apr 2011 13:02:40 +0300 [thread overview]
Message-ID: <4DAEAF40.6050207@redhat.com> (raw)
In-Reply-To: <cover.1303118779.git.jan.kiszka@siemens.com>
On 04/18/2011 12:26 PM, Jan Kiszka wrote:
> Recent merge with upstream left some corners of qemu-kvm broken behind.
> This series addresses those I've spotted based on my merge experiments
> in the past months.
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-20 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 9:26 [PATCH 0/4] qemu-kvm: Sort out upstream merge regressions Jan Kiszka
2011-04-18 9:26 ` [PATCH 1/4] qemu-kvm: Map run_on_cpu on qemu-kvm variant Jan Kiszka
2011-04-18 9:26 ` [PATCH 2/4] qemu-kvm: Synchronize states before reset Jan Kiszka
2011-04-18 9:26 ` [PATCH 3/4] qemu-kvm: Process async MCE events in main loop Jan Kiszka
2011-04-18 9:26 ` [PATCH 4/4] qemu-kvm: Unbreak guest debugging Jan Kiszka
2011-04-20 10:02 ` 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=4DAEAF40.6050207@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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;
as well as URLs for NNTP newsgroup(s).