From: "Cédric Le Goater" <clg@kaod.org>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, <qemu-devel@nongnu.org>
Cc: thuth@redhat.com, qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH for-7.0 v2 0/2] change ivshmem endianness to LITTLE_ENDIAN
Date: Wed, 15 Dec 2021 17:35:23 +0100 [thread overview]
Message-ID: <2b147241-09e6-3e7e-cd67-a0950aa031c0@kaod.org> (raw)
In-Reply-To: <20211124092948.335389-1-danielhb413@gmail.com>
On 11/24/21 10:29, 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
Applied to ppc-next.
Thanks,
C.
prev parent reply other threads:[~2021-12-15 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 9:29 [PATCH for-7.0 v2 0/2] change ivshmem endianness to LITTLE_ENDIAN Daniel Henrique Barboza
2021-11-24 9:29 ` [PATCH for-7.0 v2 1/2] ivshmem.c: change " Daniel Henrique Barboza
2021-11-24 11:28 ` Philippe Mathieu-Daudé
2021-11-24 11:33 ` Daniel Henrique Barboza
2021-11-24 12:55 ` Markus Armbruster
2021-11-24 13:09 ` Daniel Henrique Barboza
2021-11-24 9:29 ` [PATCH for-7.0 v2 2/2] ivshmem-test.c: enable test_ivshmem_server for ppc64 arch Daniel Henrique Barboza
2021-11-24 11:29 ` Philippe Mathieu-Daudé
2021-12-15 16:35 ` 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=2b147241-09e6-3e7e-cd67-a0950aa031c0@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 \
--cc=thuth@redhat.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).