From: Gleb Natapov <gleb@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Carsten Otte <cotte@de.ibm.com>, KVM <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v4 6/6] KVM: s390: Wire up ioeventfd.
Date: Thu, 28 Feb 2013 12:24:19 +0200 [thread overview]
Message-ID: <20130228102419.GW23616@redhat.com> (raw)
In-Reply-To: <20130228112013.39fb7974@gondolin>
On Thu, Feb 28, 2013 at 11:20:13AM +0100, Cornelia Huck wrote:
> Whoops. Doesn't seem to have hurt, though.
>
> v6 will come up shortly.
>
Are you going to skip v5?
--
Gleb.
next prev parent reply other threads:[~2013-02-28 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 9:22 [PATCH v4 0/6] kvm: Make ioeventfd usable on s390 Cornelia Huck
2013-02-28 9:22 ` [PATCH v4 1/6] virtio_ccw: pass a cookie value to kvm hypercall Cornelia Huck
2013-02-28 9:22 ` [PATCH v4 2/6] KVM: s390: Export virtio-ccw api Cornelia Huck
2013-02-28 9:22 ` [PATCH v4 3/6] KVM: Initialize irqfd from kvm_init() Cornelia Huck
2013-04-03 0:40 ` Sasha Levin
2013-04-03 0:40 ` [Qemu-devel] " Sasha Levin
2013-04-03 11:32 ` Cornelia Huck
2013-04-03 11:32 ` [Qemu-devel] " Cornelia Huck
2013-02-28 9:22 ` [PATCH v4 4/6] KVM: Introduce KVM_VIRTIO_CCW_NOTIFY_BUS Cornelia Huck
2013-02-28 9:22 ` [PATCH v4 5/6] KVM: ioeventfd for virtio-ccw devices Cornelia Huck
2013-02-28 9:22 ` [PATCH v4 6/6] KVM: s390: Wire up ioeventfd Cornelia Huck
2013-02-28 9:50 ` Michael S. Tsirkin
2013-02-28 10:20 ` Cornelia Huck
2013-02-28 10:24 ` Gleb Natapov [this message]
2013-02-28 11:15 ` Cornelia Huck
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=20130228102419.GW23616@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=schwidefsky@de.ibm.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 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.