qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>,
	"Cédric Le Goater" <clg@redhat.com>,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Steven Lee" <steven_lee@aspeedtech.com>,
	"Troy Lee" <leetroy@gmail.com>,
	"Jamin Lin" <jamin_lin@aspeedtech.com>,
	"Andrew Jeffery" <andrew@codeconstruct.com.au>,
	"Joel Stanley" <joel@jms.id.au>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] aspeed/{xdma, rtc, sdhci}: Fix endianness to DEVICE_LITTLE_ENDIAN
Date: Wed, 26 Nov 2025 11:27:58 +0100	[thread overview]
Message-ID: <5ce49d32-cabf-422e-a9f2-2972c1b4fdd9@redhat.com> (raw)
In-Reply-To: <b8170e28-e4ba-479c-bbbb-1b94a2fca81c@tls.msk.ru>

On 11/26/25 07:48, Michael Tokarev wrote:
> On 11/25/25 17:26, Cédric Le Goater via wrote:
>> When the XDMA, RTC and SDHCI device models of the Aspeed SoCs were
>> first introduced, their MMIO regions inherited of a DEVICE_NATIVE_ENDIAN
>> endianness. It should be DEVICE_LITTLE_ENDIAN. Fix that.
> 
> This looks like another bit for qemu-stable.  I'm picking it up
> for 10.0 and 10.1 series.  Please let me know if I shouldn't.

You can. It shouldn't harm anyone.

Thanks,

C.




      reply	other threads:[~2025-11-26 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 14:26 [PATCH] aspeed/{xdma, rtc, sdhci}: Fix endianness to DEVICE_LITTLE_ENDIAN Cédric Le Goater via
2025-11-25 15:38 ` [PATCH] aspeed/{xdma,rtc,sdhci}: " Philippe Mathieu-Daudé
2025-11-25 17:35   ` Cédric Le Goater
2025-11-25 21:51 ` Philippe Mathieu-Daudé
2025-11-26  6:48 ` [PATCH] aspeed/{xdma, rtc, sdhci}: " Michael Tokarev
2025-11-26 10:27   ` Cédric Le Goater [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=5ce49d32-cabf-422e-a9f2-2972c1b4fdd9@redhat.com \
    --to=clg@redhat.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=jamin_lin@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=leetroy@gmail.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=steven_lee@aspeedtech.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).