From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/4] hw/misc: move vmlaunchupdate.c to system_ss
Date: Fri, 6 Nov 2026 17:18:32 +0000 [thread overview]
Message-ID: <20261106171836.2020151-1-berrange@redhat.com> (raw)
If building with IGVM enabled and both arm-softmmu and
aarch64-softmmu, test-multi-target breaks because the
vm-launch-update QOM class is linked in twice and thus
registered twice.
Daniel P. Berrangé (4):
hw/misc: move vmlaunchupdate.c from specific_ss to system_ss
tests/lcitool: add mips32r6el toolchain to refresh script
tests/docker: add igvm to Fedora container images
MAINTAINERS: fix typo in test-multi-target.c filename
MAINTAINERS | 2 +-
hw/misc/meson.build | 2 +-
tests/docker/dockerfiles/fedora-rust-nightly.docker | 1 +
tests/docker/dockerfiles/fedora.docker | 1 +
tests/lcitool/projects/qemu.yml | 1 +
tests/lcitool/refresh | 2 ++
6 files changed, 7 insertions(+), 2 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-06 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:18 Daniel P. Berrangé [this message]
2026-11-06 17:18 ` [PATCH 1/4] hw/misc: move vmlaunchupdate.c from specific_ss to system_ss Daniel P. Berrangé
2026-11-06 17:18 ` [PATCH 2/4] tests/lcitool: add mips32r6el toolchain to refresh script Daniel P. Berrangé
2026-11-09 11:04 ` Philippe Mathieu-Daudé
2026-11-06 17:18 ` [PATCH 3/4] tests/docker: add igvm to Fedora container images Daniel P. Berrangé
2026-11-06 17:18 ` [PATCH 4/4] MAINTAINERS: fix typo in test-multi-target.c filename Daniel P. Berrangé
2026-11-06 17:47 ` [PATCH 0/4] hw/misc: move vmlaunchupdate.c to system_ss Pierrick Bouvier
2026-11-06 23:18 ` Pierrick Bouvier
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=20261106171836.2020151-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jiaxun.yang@flygoat.com \
--cc=philmd@oss.qualcomm.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@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.