From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] kvm-unittests: Fix apic unittest for latest qemu-kvm
Date: Mon, 14 May 2012 11:30:59 +0300 [thread overview]
Message-ID: <4FB0C2C3.7000501@redhat.com> (raw)
In-Reply-To: <1336490230-22411-1-git-send-email-joerg.roedel@amd.com>
On 05/08/2012 06:17 PM, Joerg Roedel wrote:
> Since commit b334ec56 in qemu-kvm the use of irqlines > 15
> is not supported anymore. This causes the apic unittest to
> fail since this commit. Since the commit-msg explicitly
> states that potential users of this needs to be fixed, here
> is the fix which uses irq lines 14 and 15 instead in the
> unittest.
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-05-14 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 15:17 [PATCH] kvm-unittests: Fix apic unittest for latest qemu-kvm Joerg Roedel
2012-05-09 1:56 ` Amos Kong
2012-05-14 8:30 ` 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=4FB0C2C3.7000501@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=joerg.roedel@amd.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).