From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: EVENTFD: remove inclusion of irq.h
Date: Thu, 11 Sep 2014 09:11:29 +0200 [thread overview]
Message-ID: <54114B21.1080102@redhat.com> (raw)
In-Reply-To: <20140911030932.GA2784@lvm>
Il 11/09/2014 05:09, Christoffer Dall ha scritto:
> On Mon, Sep 01, 2014 at 12:11:19PM +0200, Paolo Bonzini wrote:
>> Il 01/09/2014 10:36, Eric Auger ha scritto:
>>> No more needed. irq.h would be void on ARM.
>>>
>>> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>>>
>>> ---
>>>
>>> I don't think irq.h is needed anymore since Paul Mackerras' work. However
>>> I did not compile for all architectures.
>>> ---
>>> virt/kvm/eventfd.c | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
>>> index 3c5981c..0c712a7 100644
>>> --- a/virt/kvm/eventfd.c
>>> +++ b/virt/kvm/eventfd.c
>>> @@ -36,7 +36,6 @@
>>> #include <linux/seqlock.h>
>>> #include <trace/events/kvm.h>
>>>
>>> -#include "irq.h"
>>> #include "iodev.h"
>>>
>>> #ifdef CONFIG_HAVE_KVM_IRQFD
>>>
>>
>> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> Christoffer, please include this via the ARM tree, together with ARM
>> irqfd support. Thanks,
>>
> Marc is dealing with the tree this week and the next so he can apply it
> to kvmarm/queue. Do you want it to wait and go with the irqfd patch
> (which has dependencies not yet resolved) or should we just queue it?
As you prefer.
Paolo
next prev parent reply other threads:[~2014-09-11 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 8:36 [PATCH] KVM: EVENTFD: remove inclusion of irq.h Eric Auger
2014-09-01 10:11 ` Paolo Bonzini
2014-09-11 3:09 ` Christoffer Dall
2014-09-11 7:11 ` Paolo Bonzini [this message]
2014-09-11 10:24 ` Marc Zyngier
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=54114B21.1080102@redhat.com \
--to=pbonzini@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).