From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-1.5?] ide-test: Fix endianness problems
Date: Wed, 15 May 2013 15:15:52 +0200 [thread overview]
Message-ID: <51938A88.3060306@redhat.com> (raw)
In-Reply-To: <1368622839-7084-1-git-send-email-kwolf@redhat.com>
Il 15/05/2013 15:00, Kevin Wolf ha scritto:
> The test case passes on big endian hosts now (tested on ppc64)
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
For 1.5? Do we need an extra -rc?
Paolo
next prev parent reply other threads:[~2013-05-15 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 13:00 [Qemu-devel] [PATCH] ide-test: Fix endianness problems Kevin Wolf
2013-05-15 13:15 ` Paolo Bonzini [this message]
2013-05-15 13:24 ` [Qemu-devel] [PATCH for-1.5?] " Kevin Wolf
2013-05-15 13:47 ` Paolo Bonzini
2013-05-15 15:37 ` Anthony Liguori
2013-05-15 16:07 ` mdroth
2013-05-16 9:04 ` [Qemu-devel] [PATCH] " Stefan Hajnoczi
2013-05-16 9:12 ` Kevin Wolf
2013-05-16 12:50 ` Anthony Liguori
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=51938A88.3060306@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).