From: Avi Kivity <avi@qumranet.com>
To: Liu Yu <yu.liu@freescale.com>
Cc: aliguori@us.ibm.com, kvm@vger.kernel.org, hollisb@us.ibm.com,
rusty@rustcorp.com.au, qemu-devel@nongnu.org,
kvm-ppc@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] virtio-blk: change config to guest endian
Date: Wed, 10 Sep 2008 18:24:41 +0300 [thread overview]
Message-ID: <48C7E6B9.1060403@qumranet.com> (raw)
In-Reply-To: <1220932102-11863-1-git-send-email-yu.liu@freescale.com>
Liu Yu wrote:
> Since virtio-blk in kernel has already changed, qemu needs to be updated.
> see http://thread.gmane.org/gmane.linux.kernel.virtualization/5776/focus=580
>
> Only tested it on branch kvm-70rc1 for e500/powerpc platform.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-09-10 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 3:48 [Qemu-devel] [PATCH] virtio-blk: change config to guest endian Liu Yu
2008-09-10 15:24 ` Avi Kivity [this message]
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=48C7E6B9.1060403@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@us.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=yu.liu@freescale.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).