From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH v8 02/15] KVM: use KVM_CAP_IRQ_ROUTING to protect the
 routing related code
Date: Mon, 18 Jun 2012 16:06:25 +0300
Message-ID: <4FDF27D1.8000406@redhat.com>
References: <20120615190553.24590.18391.stgit@ubuntu> <20120615190702.24590.10425.stgit@ubuntu>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: android-virt@lists.cs.columbia.edu, kvm@vger.kernel.org
To: Christoffer Dall <c.dall@virtualopensystems.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:59976 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751629Ab2FRNGe (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 18 Jun 2012 09:06:34 -0400
In-Reply-To: <20120615190702.24590.10425.stgit@ubuntu>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 06/15/2012 10:07 PM, Christoffer Dall wrote:
> From: Marc Zyngier <marc.zyngier@arm.com>
> 
> The KVM code sometimes uses CONFIG_HAVE_KVM_IRQCHIP to protect
> code that is related to IRQ routing, which not all in-kernel
> irqchips may support.
> 
> Use KVM_CAP_IRQ_ROUTING instead.

Thanks, applied.


-- 
error compiling committee.c: too many arguments to function