From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>
Subject: [PULL 00/10] Fixes for QEMU v10.2rc2
Date: Fri, 21 Nov 2025 10:38:02 +0100 [thread overview]
Message-ID: <20251121093812.280911-1-thuth@redhat.com> (raw)
Hi Richard!
The following changes since commit 5a5b06d2f6f71d7789719b97143fc5b543bec07a:
Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2025-11-20 08:12:59 +0100)
are available in the Git repository at:
https://gitlab.com/thuth/qemu.git tags/pull-request-2025-11-21
for you to fetch changes up to 88175cff49dedd709b7a01e0e5e1bdcad69e0c8d:
MAINTAINERS: s390 maintainer updates (2025-11-21 08:34:53 +0100)
----------------------------------------------------------------
* Fix a crash that occurs when passing through virtio devices to nested guest
* Update s390x MAINTAINERS
* Fix various pylint warnings in functional tests
----------------------------------------------------------------
David Hildenbrand (Red Hat) (1):
MAINTAINERS: s390 maintainer updates
Thomas Huth (9):
hw/s390x: Fix a possible crash with passed-through virtio devices
tests/functional/arm/test_aspeed_ast2600_buildroot: Fix pylint warnings
tests/functional/x86_64/test_virtio_gpu: Fix various issues reported by pylint
tests/functional/x86_64/test_reverse_debug: Silence pylint warning
tests/functional/x86_64/test_memlock: Silence pylint warnings
tests/functional/ppc/test_amiga: Fix issues reported by pylint and flake8
tests/functional/ppc/test_ppe42: Fix style issues reported by pylint
tests/functional/aarch64/test_reverse_debug: Fix issues reported by pylint
tests/functional/aarch64/test_rme_sbsaref: Silence issues reported by pylint
MAINTAINERS | 9 ++--
hw/s390x/s390-hypercall.c | 14 ++++++
tests/functional/aarch64/test_reverse_debug.py | 4 +-
tests/functional/aarch64/test_rme_sbsaref.py | 3 +-
.../arm/test_aspeed_ast2600_buildroot.py | 21 ++++----
tests/functional/ppc/test_amiga.py | 6 +--
tests/functional/ppc/test_ppe42.py | 14 +++---
tests/functional/x86_64/test_memlock.py | 6 ++-
tests/functional/x86_64/test_reverse_debug.py | 2 +-
tests/functional/x86_64/test_virtio_gpu.py | 56 +++++++++++-----------
10 files changed, 76 insertions(+), 59 deletions(-)
next reply other threads:[~2025-11-21 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 9:38 Thomas Huth [this message]
2025-11-21 9:38 ` [PULL 01/10] hw/s390x: Fix a possible crash with passed-through virtio devices Thomas Huth
2025-11-21 9:38 ` [PULL 02/10] tests/functional/arm/test_aspeed_ast2600_buildroot: Fix pylint warnings Thomas Huth
2025-11-21 9:38 ` [PULL 03/10] tests/functional/x86_64/test_virtio_gpu: Fix various issues reported by pylint Thomas Huth
2025-11-21 9:38 ` [PULL 04/10] tests/functional/x86_64/test_reverse_debug: Silence pylint warning Thomas Huth
2025-11-21 9:38 ` [PULL 05/10] tests/functional/x86_64/test_memlock: Silence pylint warnings Thomas Huth
2025-11-21 9:38 ` [PULL 06/10] tests/functional/ppc/test_amiga: Fix issues reported by pylint and flake8 Thomas Huth
2025-11-21 9:38 ` [PULL 07/10] tests/functional/ppc/test_ppe42: Fix style issues reported by pylint Thomas Huth
2025-11-21 9:38 ` [PULL 08/10] tests/functional/aarch64/test_reverse_debug: Fix " Thomas Huth
2025-11-21 9:38 ` [PULL 09/10] tests/functional/aarch64/test_rme_sbsaref: Silence " Thomas Huth
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=20251121093812.280911-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).