From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Carsten Otte <cotte@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>
Subject: Re: [PATCH v5 0/3] s390: Guest support for virtio-ccw.
Date: Tue, 18 Dec 2012 09:13:09 +0100 [thread overview]
Message-ID: <50D02595.8040208@de.ibm.com> (raw)
In-Reply-To: <7613CB93-4C0D-4B68-B473-05DF99FE1EE9@suse.de>
On 17/12/12 16:00, Alexander Graf wrote:
>
> On 14.12.2012, at 17:02, Cornelia Huck wrote:
>
>> Hi,
>>
>> here's the virtio-ccw guest support for kvm/next again.
>>
>> The not-kvm specific patches have made their way upstream via the
>> s390 tree in the meantime. Patch 2 fixes an inconsistency there.
>>
>> Patch 3 lost the now unneeded schid.h include; otherwise, the patches
>> are unchanged from v4.
>
> Reviewed-by: Alexander Graf <agraf@suse.de>
Marcelo, Gleb,
can you add those patches to the KVM next tree?
Christian
next prev parent reply other threads:[~2012-12-18 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 16:02 [PATCH v5 0/3] s390: Guest support for virtio-ccw Cornelia Huck
2012-12-14 16:02 ` [PATCH 1/3] KVM: s390: Handle hosts not supporting s390-virtio Cornelia Huck
2012-12-14 16:02 ` [PATCH 2/3] s390/ccwdev: Include asm/schid.h Cornelia Huck
2012-12-14 16:02 ` [PATCH 3/3] KVM: s390: Add a channel I/O based virtio transport driver Cornelia Huck
2012-12-17 15:00 ` [PATCH v5 0/3] s390: Guest support for virtio-ccw Alexander Graf
2012-12-18 8:13 ` Christian Borntraeger [this message]
2012-12-18 12:37 ` Gleb Natapov
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=50D02595.8040208@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=gleb@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.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.