From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [PATCH 0/5] hw/arm: Remove big-endian checks on machine code
Date: Sat, 29 Feb 2020 11:38:49 -0800 [thread overview]
Message-ID: <0899e78b-0082-a826-2e15-b44c76e6c716@linaro.org> (raw)
In-Reply-To: <20200228125351.29482-1-philmd@redhat.com>
On 2/28/20 4:53 AM, Philippe Mathieu-Daudé wrote:
> We only build the little-endian softmmu configurations.
> Checking for big endian is pointless, remove the unused code.
>
> Philippe Mathieu-Daudé (5):
> hw/arm/gumstix: Simplify since the machines are little-endian only
> hw/arm/mainstone: Simplify since the machines are little-endian only
> hw/arm/omap_sx1: Simplify since the machines are little-endian only
> hw/arm/z2: Simplify since the machines are little-endian only
> hw/arm/musicpal: Simplify since the machines are little-endian only
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2020-02-29 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 12:53 [PATCH 0/5] hw/arm: Remove big-endian checks on machine code Philippe Mathieu-Daudé
2020-02-28 12:53 ` [PATCH 1/5] hw/arm/gumstix: Simplify since the machines are little-endian only Philippe Mathieu-Daudé
2020-02-28 12:53 ` [PATCH 2/5] hw/arm/mainstone: " Philippe Mathieu-Daudé
2020-02-28 12:53 ` [PATCH 3/5] hw/arm/omap_sx1: " Philippe Mathieu-Daudé
2020-02-28 12:53 ` [PATCH 4/5] hw/arm/z2: " Philippe Mathieu-Daudé
2020-02-28 12:53 ` [PATCH 5/5] hw/arm/musicpal: " Philippe Mathieu-Daudé
2020-02-29 19:38 ` Richard Henderson [this message]
2020-03-02 11:44 ` [PATCH 0/5] hw/arm: Remove big-endian checks on machine code Peter Maydell
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=0899e78b-0082-a826-2e15-b44c76e6c716@linaro.org \
--to=richard.henderson@linaro.org \
--cc=jan.kiszka@web.de \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--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).