From: "Cédric Le Goater" <clg@kaod.org>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, <qemu-devel@nongnu.org>
Cc: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH 0/2] change IVSHMEM endianess to LITTLE_ENDIAN
Date: Wed, 24 Nov 2021 00:22:14 +0100 [thread overview]
Message-ID: <a6b4bfd8-099c-9e7a-0492-6df404167367@kaod.org> (raw)
In-Reply-To: <20211123211932.284043-1-danielhb413@gmail.com>
On 11/23/21 22:19, Daniel Henrique Barboza wrote:
> Hi,
>
> This small series fixes an issue reported in Gitlab [1] that
> affects PowerPC big-endian and little-endian and probably all
> other big-endians in the wild that might use 'ivshmem'.
>
> It's not clear to me who is the maintainer/responsible for this device
> (MAINTAINERS doesn't seem to have any 'ivhshmem' entries nor someone
> that looks upon all hw/misc/* files) so I didn't add any CC in that
> regard. 'qemu-ppc' is being copied for awareness since they are the
> folks that are most likely being impacted by the bug.
>
> [1] https://gitlab.com/qemu-project/qemu/-/issues/168
Do we want these fixes for 6.2 ?
Thanks,
C.
>
> Daniel Henrique Barboza (2):
> ivshmem.c: change endianness to LITTLE_ENDIAN
> ivshmem-test.c: enable test_ivshmem_server for ppc64 arch
>
> hw/misc/ivshmem.c | 2 +-
> tests/qtest/ivshmem-test.c | 5 +----
> 2 files changed, 2 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2021-11-23 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 21:19 [PATCH 0/2] change IVSHMEM endianess to LITTLE_ENDIAN Daniel Henrique Barboza
2021-11-23 21:19 ` [PATCH 1/2] ivshmem.c: change endianness " Daniel Henrique Barboza
2021-11-23 21:19 ` [PATCH 2/2] ivshmem-test.c: enable test_ivshmem_server for ppc64 arch Daniel Henrique Barboza
2021-11-24 7:35 ` Thomas Huth
2021-11-23 23:22 ` Cédric Le Goater [this message]
2021-11-24 9:21 ` [PATCH 0/2] change IVSHMEM endianess to LITTLE_ENDIAN Daniel Henrique Barboza
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=a6b4bfd8-099c-9e7a-0492-6df404167367@kaod.org \
--to=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.