From: Paolo Bonzini <pbonzini@redhat.com>
To: Ljun <1275151072@qq.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] =?gb18030?b?u9i4tKO6UmU6IFdoeSBkb2VzIHFlbXUgbm90IHN1?= =?gb18030?q?pport_qemu-system-armeb=3F?=
Date: Mon, 16 Jun 2014 16:52:14 +0200 [thread overview]
Message-ID: <539F049E.9010404@redhat.com> (raw)
In-Reply-To: <tencent_10F11DF35D1B1C76206D9165@qq.com>
Il 16/06/2014 15:17, Ljun ha scritto:
> I am very glad to you have finished the patch for qemu-system-armeb.I
> have seriously read your patch in 29 May about the armeb. I want to know
> two points:
> 1) whether combined your patch into the qemu , it can support
> qemu-system-armeb .Do I need to do otherthings?
Actually the binary will still be called qemu-system-arm, and should
support both endiannesses.
> 2) whether you have a plan to verify the patch and submit it?
I plan to send it this week. Help with testing will be welcome.
Paolo
prev parent reply other threads:[~2014-06-16 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 13:49 [Qemu-devel] Why does qemu not support qemu-system-armeb? Ljun
2014-06-15 9:08 ` Peter Maydell
2014-06-15 13:58 ` Paolo Bonzini
[not found] ` <tencent_10F11DF35D1B1C76206D9165@qq.com>
2014-06-16 14:52 ` Paolo Bonzini [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=539F049E.9010404@redhat.com \
--to=pbonzini@redhat.com \
--cc=1275151072@qq.com \
--cc=qemu-devel@nongnu.org \
/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).