From: Thomas Huth <thuth@redhat.com>
To: Rakesh Jeyasingh <rakeshjb010@gmail.com>,
qemu-devel@nongnu.org, philmd@linaro.org
Cc: pbonzini@redhat.com, balaton@eik.bme.hu
Subject: Re: [PATCH v5 0/2] GT64120 PCI endianness fixes and cleanup
Date: Fri, 16 May 2025 20:14:41 +0200 [thread overview]
Message-ID: <1fd458bd-f390-4d4b-acde-465f28e0dea8@redhat.com> (raw)
In-Reply-To: <20250429170354.150581-1-rakeshjb010@gmail.com>
On 29/04/2025 19.03, Rakesh Jeyasingh wrote:
> Changes since v4:
> 1.Introduced needs_bswap() helper for clean endianness logic
> 2.use the existing pci_host_data_le_ops.read/write from hw/pci/pci_host.c
>
> v4:https://patchew.org/QEMU/20250331184820.34673-1-rakeshjb010@gmail.com/
>
> Rakesh Jeyasingh (2):
> hw/pci-host/gt64120: Fix endianness handling
> hw/pci-host: Remove unused pci_host_data_be_ops
>
> hw/pci-host/gt64120.c | 82 ++++++++++++++++++++++----------------
> hw/pci/pci_host.c | 6 ---
> include/hw/pci-host/dino.h | 4 --
> include/hw/pci/pci_host.h | 1 -
> 4 files changed, 48 insertions(+), 45 deletions(-)
Thanks for tackling this ... I gave it a try on both, little and big endian
host and it seems to work as expected now.
Series
Tested-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2025-05-16 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 17:03 [PATCH v5 0/2] GT64120 PCI endianness fixes and cleanup Rakesh Jeyasingh
2025-04-29 17:03 ` [PATCH v5 1/2] hw/pci-host/gt64120: Fix endianness handling Rakesh Jeyasingh
2025-05-17 5:25 ` Rakesh Jeyasingh
2025-05-17 14:16 ` Paolo Bonzini
2025-05-22 11:32 ` Michael Tokarev
2025-04-29 17:03 ` [PATCH v5 2/2] hw/pci-host: Remove unused pci_host_data_be_ops Rakesh Jeyasingh
2025-05-16 18:14 ` Thomas Huth [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=1fd458bd-f390-4d4b-acde-465f28e0dea8@redhat.com \
--to=thuth@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rakeshjb010@gmail.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).