From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH v3 00/10] qemu-kvm: Switch to upstream irqchip services
Date: Wed, 07 Mar 2012 12:30:54 +0200 [thread overview]
Message-ID: <4F5738DE.6040802@redhat.com> (raw)
In-Reply-To: <cover.1330680649.git.jan.kiszka@siemens.com>
On 03/02/2012 11:30 AM, Jan Kiszka wrote:
> Now that upstream has basic irqchip support, we can make use of it for
> qemu-kvm as well, removing another 700 lines of code here.
>
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-07 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 9:30 [PATCH v3 00/10] qemu-kvm: Switch to upstream irqchip services Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 01/10] qemu-kvm: Move kvm_create_pit out of arch init code Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 02/10] qemu-kvm: Use machine options to configure qemu-kvm defaults Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 03/10] qemu-kvm: Use upstream irq routing services Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 04/10] qemu-kvm: Use upstream kvm_irqchip_create Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 05/10] qemu-kvm: Use upstream kvm-ioapic Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 06/10] qemu-kvm: Use upstream kvm-i8259 Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 07/10] qemu-kvm: Drop unused kvm_get/set_irqchip Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 08/10] qemu-kvm: Use upstream kvm_irqchip_set_irq instead of kvm_set_irq Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 09/10] qemu-kvm: Use upstream kvm-apic Jan Kiszka
2012-03-02 9:30 ` [PATCH v3 10/10] qemu-kvm: Remove some spurious whitespace diffs to upstream Jan Kiszka
2012-03-07 10: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=4F5738DE.6040802@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.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).