From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "agraf@suse.de" <agraf@suse.de>,
"Anthony Liguori" <aliguori@us.ibm.com>,
"Ben Collins" <bcollins@ubuntu.com>,
"Andreas Färber" <afaerber@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] kvm: Fix build for non-CAP_IRQ_ROUTING targets
Date: Wed, 06 Jun 2012 13:44:48 +0300 [thread overview]
Message-ID: <4FCF34A0.6030101@redhat.com> (raw)
In-Reply-To: <4FCF3165.6040409@siemens.com>
On 06/06/2012 01:31 PM, Jan Kiszka wrote:
> On 2012-06-06 10:41, Avi Kivity wrote:
>> On 06/05/2012 10:03 PM, Jan Kiszka wrote:
>>> A type definition and a KVMState field initialization escaped the
>>> required wrapping with KVM_CAP_IRQ_ROUTING. Also, we need to provide a
>>> dummy kvm_irqchip_release_virq as virtio-pci references (but does not
>>> use) it.
>>>
>>
>> Thanks, applied.
>
> Please send a pull soon.
It was posted already, I just forgot to copy you.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-06-06 10:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 23:33 [Qemu-devel] buildbot failure in qemu on default_ppc qemu
2012-06-05 0:54 ` Andreas Färber
2012-06-05 0:58 ` Anthony Liguori
2012-06-05 1:00 ` Alexander Graf
2012-06-05 1:04 ` Anthony Liguori
2012-06-05 1:09 ` Alexander Graf
2012-06-05 7:35 ` Jan Kiszka
2012-06-05 7:31 ` [Qemu-devel] [PATCH] kvm: Fix build for non-CAP_IRQ_ROUTING targets Jan Kiszka
2012-06-05 19:03 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2012-06-05 19:53 ` Ben Collins
2012-06-06 0:24 ` Andreas Färber
2012-06-06 8:41 ` Avi Kivity
2012-06-06 10:31 ` Jan Kiszka
2012-06-06 10:44 ` Avi Kivity [this message]
2012-06-06 11:06 ` Anthony Liguori
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=4FCF34A0.6030101@redhat.com \
--to=avi@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=bcollins@ubuntu.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).