From: Rusty Russell <rusty@rustcorp.com.au>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Carsten Otte <cotte@de.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avi Kivity <avi@redhat.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v2] virtio-spec: Add virtio-ccw spec.
Date: Thu, 06 Sep 2012 11:56:31 +0930 [thread overview]
Message-ID: <87ehmfj38o.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1346771641-12136-2-git-send-email-cornelia.huck@de.ibm.com>
Cornelia Huck <cornelia.huck@de.ibm.com> writes:
> Add specifications for the new s390 specific virtio-ccw transport.
>
> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Excellent. I have applied and pushed this revision.
I was tempted to ask for an explicit endian marker, as switching to
explicit little endian was high on the TODO list for virtio2. On the
other hand, we could say virtio2-pci config space is always
little-endian, and virtio-ccw config space is always big-endian.
That covers the config endian, and and if we introduce a new ring
format, that endian debate can be separate.
Cheers,
Rusty.
next prev parent reply other threads:[~2012-09-06 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 15:14 [RFC PATCH v2] Update virtio spec for virtio-ccw Cornelia Huck
2012-09-04 15:14 ` [PATCH v2] virtio-spec: Add virtio-ccw spec Cornelia Huck
2012-09-06 2:26 ` Rusty Russell [this message]
2012-09-06 3:09 ` Benjamin Herrenschmidt
2012-09-06 13:51 ` Cornelia Huck
2012-09-06 23:57 ` Rusty Russell
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=87ehmfj38o.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--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=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox