All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Ben Collins <bcollins@ubuntu.com>,
	qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH v2] kvm: Fix build for non-CAP_IRQ_ROUTING targets
Date: Wed, 06 Jun 2012 02:24:59 +0200	[thread overview]
Message-ID: <4FCEA35B.4050200@suse.de> (raw)
In-Reply-To: <4FCE581D.8020309@siemens.com>

Am 05.06.2012 21:03, schrieb Jan Kiszka:
> 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.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Tested-by: Andreas Färber <afaerber@suse.de>

Thanks,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2012-06-06  0:27 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 [this message]
2012-06-06  8:41       ` Avi Kivity
2012-06-06 10:31         ` Jan Kiszka
2012-06-06 10:44           ` Avi Kivity
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=4FCEA35B.4050200@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.