From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: Artyom Tarasenko <atar4qemu@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Richard Henderson <richard.henderson@linaro.org>,
xen-devel@lists.xenproject.org,
Paolo Bonzini <pbonzini@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Anthony PERARD <anthony@xenproject.org>,
Eduardo Habkost <eduardo@habkost.net>,
Thomas Huth <huth@tuxfamily.org>, Jia Liu <proljc@gmail.com>,
Stafford Horne <shorne@gmail.com>, Paul Durrant <paul@xen.org>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/5] hw: Mark architecture specific devices with specific endianness
Date: Mon, 30 Dec 2024 17:42:07 +0100 [thread overview]
Message-ID: <20fbbcc8-bf6d-44c2-b904-be52debc1f8a@linaro.org> (raw)
In-Reply-To: <20241106184612.71897-1-philmd@linaro.org>
On 6/11/24 19:46, Philippe Mathieu-Daudé wrote:
> When a device is only built for an architecture built for
> a particular endianness, we can simplify the device to not
> use the "target native endianness" definition and directly
> use the proper target endianness.
>
> Philippe Mathieu-Daudé (5):
> hw/i386: Mark devices as little-endian
> hw/tricore: Mark devices as little-endian
> hw/m68k: Mark devices as big-endian
> hw/openrisc: Mark devices as big-endian
> hw/sparc: Mark devices as big-endian
I'm queuing this series, better to test it early in the dev cycle.
prev parent reply other threads:[~2024-12-30 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:46 [PATCH 0/5] hw: Mark architecture specific devices with specific endianness Philippe Mathieu-Daudé
2024-11-06 18:46 ` [PATCH 1/5] hw/i386: Mark devices as little-endian Philippe Mathieu-Daudé
2024-11-07 9:59 ` Richard Henderson
2024-11-09 6:39 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 2/5] hw/tricore: " Philippe Mathieu-Daudé
2024-11-07 10:01 ` Richard Henderson
2024-11-09 6:38 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 3/5] hw/m68k: Mark devices as big-endian Philippe Mathieu-Daudé
2024-11-07 10:02 ` Richard Henderson
2024-11-09 6:28 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 4/5] hw/openrisc: " Philippe Mathieu-Daudé
2024-11-07 10:03 ` Richard Henderson
2024-11-09 6:42 ` Thomas Huth
2024-11-09 15:58 ` Philippe Mathieu-Daudé
2024-11-09 18:08 ` Richard Henderson
2024-11-09 18:40 ` Thomas Huth
2024-11-06 18:46 ` [PATCH 5/5] hw/sparc: " Philippe Mathieu-Daudé
2024-11-06 22:56 ` Mark Cave-Ayland
2024-11-07 10:04 ` Richard Henderson
2024-12-30 16:42 ` Philippe Mathieu-Daudé [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=20fbbcc8-bf6d-44c2-b904-be52debc1f8a@linaro.org \
--to=philmd@linaro.org \
--cc=anthony@xenproject.org \
--cc=atar4qemu@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=eduardo@habkost.net \
--cc=huth@tuxfamily.org \
--cc=kbastian@mail.uni-paderborn.de \
--cc=marcel.apfelbaum@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shorne@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).