All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	qemu-devel@nongnu.org
Cc: agraf@suse.de, gleb@kernel.org
Subject: Re: [PATCH v3 0/4] KVM: irqfds for s390
Date: Mon, 24 Mar 2014 11:40:16 +0100	[thread overview]
Message-ID: <53300B90.7090301@redhat.com> (raw)
In-Reply-To: <532FF0E1.5000502@de.ibm.com>

Il 24/03/2014 09:46, Christian Borntraeger ha scritto:
>> > here's the next iteration of my patchset introducing irqfds for s390.
>> >
>> > Changes from v2:
>> > - rebased against current kvm/queue
>> > - kvm common code lock fix is already in queue
>> > - move some changes that belonged in patch 2 from patch 3
>> > - add a limit for mapped pages to patch 2
>> > - collected some acks
>> >
>> > Changes from v1:
>> > - rebased against current kvm/queue, bumping capability numbers
>> > - guest adapter interrupt support is already in the kvm tree
>> >
>> > Again, find it on
>> >
>> > git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git kvms390-irqfd
> Looks all good.
>
> Paolo,
>
> I guess this will miss the next merge window,  but can you pull for kvm/queue
> if you have no further comments?

I think this can get into the next merge window, no problem.

I plan to move kvm/queue -> kvm/next tomorrow or wednesday, and include 
this series.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	qemu-devel@nongnu.org
Cc: gleb@kernel.org, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 0/4] KVM: irqfds for s390
Date: Mon, 24 Mar 2014 11:40:16 +0100	[thread overview]
Message-ID: <53300B90.7090301@redhat.com> (raw)
In-Reply-To: <532FF0E1.5000502@de.ibm.com>

Il 24/03/2014 09:46, Christian Borntraeger ha scritto:
>> > here's the next iteration of my patchset introducing irqfds for s390.
>> >
>> > Changes from v2:
>> > - rebased against current kvm/queue
>> > - kvm common code lock fix is already in queue
>> > - move some changes that belonged in patch 2 from patch 3
>> > - add a limit for mapped pages to patch 2
>> > - collected some acks
>> >
>> > Changes from v1:
>> > - rebased against current kvm/queue, bumping capability numbers
>> > - guest adapter interrupt support is already in the kvm tree
>> >
>> > Again, find it on
>> >
>> > git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git kvms390-irqfd
> Looks all good.
>
> Paolo,
>
> I guess this will miss the next merge window,  but can you pull for kvm/queue
> if you have no further comments?

I think this can get into the next merge window, no problem.

I plan to move kvm/queue -> kvm/next tomorrow or wednesday, and include 
this series.

Paolo

  reply	other threads:[~2014-03-24 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 12:52 [PATCH v3 0/4] KVM: irqfds for s390 Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] " Cornelia Huck
2014-03-21 12:52 ` [PATCH v3 1/4] KVM: Add per-vm capability enablement Cornelia Huck
2014-03-21 12:52   ` [Qemu-devel] " Cornelia Huck
2014-03-21 12:52 ` [PATCH v3 2/4] KVM: s390: adapter interrupt sources Cornelia Huck
2014-03-21 12:52   ` [Qemu-devel] " Cornelia Huck
2014-03-21 12:52 ` [PATCH v3 3/4] KVM: s390: irq routing for adapter interrupts Cornelia Huck
2014-03-21 12:52   ` [Qemu-devel] " Cornelia Huck
2014-03-21 12:52 ` [PATCH v3 4/4] KVM: Bump KVM_MAX_IRQ_ROUTES for s390 Cornelia Huck
2014-03-21 12:52   ` [Qemu-devel] " Cornelia Huck
2014-03-24  8:46 ` [PATCH v3 0/4] KVM: irqfds " Christian Borntraeger
2014-03-24  8:46   ` [Qemu-devel] " Christian Borntraeger
2014-03-24 10:40   ` Paolo Bonzini [this message]
2014-03-24 10:40     ` Paolo Bonzini

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=53300B90.7090301@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --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.