From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, thuth@linux.vnet.ibm.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] virtio-ccw: assure BE accesses
Date: Fri, 13 Mar 2015 10:44:45 +0100 [thread overview]
Message-ID: <20150313104445.199e229d.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1426067871-17693-2-git-send-email-cornelia.huck@de.ibm.com>
On Wed, 11 Mar 2015 10:57:50 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> All fields in structures transmitted by ccws are big endian; assure
> we handle them as such.
>
> Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>
> Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
> hw/s390x/virtio-ccw.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
Applied to my s390-next branch.
next prev parent reply other threads:[~2015-03-13 9:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 13:32 [Qemu-devel] [PATCH] virtio: avoid leading underscores for helpers Cornelia Huck
2015-03-10 14:12 ` Michael S. Tsirkin
2015-03-10 14:22 ` Cornelia Huck
2015-03-10 14:27 ` Michael S. Tsirkin
2015-03-10 16:03 ` Cornelia Huck
2015-03-10 16:34 ` Michael S. Tsirkin
2015-03-10 17:05 ` Cornelia Huck
2015-03-10 17:22 ` [Qemu-devel] [PATCH] virtio: legacy features callback Cornelia Huck
2015-03-11 9:57 ` [Qemu-devel] [PATCH 0/2] virtio-ccw: be accesses Cornelia Huck
2015-03-11 9:57 ` [Qemu-devel] [PATCH 1/2] virtio-ccw: assure BE accesses Cornelia Huck
2015-03-13 9:44 ` Cornelia Huck [this message]
2015-03-11 9:57 ` [Qemu-devel] [PATCH 2/2] virtio-ccw: assure be accesses for set-revision Cornelia Huck
2015-03-11 12:39 ` Thomas Huth
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=20150313104445.199e229d.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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;
as well as URLs for NNTP newsgroup(s).