qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PULL 0/8] Functional and s390x patches for v10.0-rc1
Date: Wed, 19 Mar 2025 14:18:43 +0100	[thread overview]
Message-ID: <20250319131851.148817-1-thuth@redhat.com> (raw)

 Hi Stefan!

The following changes since commit 1dae461a913f9da88df05de6e2020d3134356f2e:

  Update version for v10.0.0-rc0 release (2025-03-18 10:18:14 -0400)

are available in the Git repository at:

  https://gitlab.com/thuth/qemu.git tags/pull-request-2025-03-19

for you to fetch changes up to f700abbbeb6ab68a3446d1fb168a934d6f284eb5:

  tests/functional/test_migration: Use "ncat" instead of "nc" in the exec test (2025-03-19 13:28:34 +0100)

----------------------------------------------------------------
* Fix linking problem when CONFIG_VIRTIO_PCI is not set for s390x
* Update functional tests parts of the documenation
* Some minor fixes for functional tests

----------------------------------------------------------------
Daniel P. Berrangé (1):
      tests/functional: remove all class level fields

Niek Linnenbank (1):
      tests/functional/test_arm_orangepi: rename test class to 'OrangePiMachine'

Thomas Huth (6):
      hw/virtio: Also include md stubs in case CONFIG_VIRTIO_PCI is not set
      docs/system: Use the meson binary from the pyvenv
      docs/system/arm: Use "functional tests" instead of "integration tests"
      docs/devel/testing/functional: Add a section about logging
      tests/functional/test_x86_64_kvm_xen: Remove avocado tags
      tests/functional/test_migration: Use "ncat" instead of "nc" in the exec test

 docs/devel/testing/functional.rst       | 22 ++++++++++++++++++++--
 docs/system/arm/bananapi_m2u.rst        |  8 ++++----
 docs/system/arm/orangepi.rst            |  8 ++++----
 docs/system/devices/igb.rst             |  5 +++--
 hw/virtio/meson.build                   |  3 ++-
 tests/functional/qemu_test/testcase.py  |  6 ------
 tests/functional/test_acpi_bits.py      |  1 -
 tests/functional/test_arm_orangepi.py   |  2 +-
 tests/functional/test_migration.py      |  7 +++----
 tests/functional/test_x86_64_kvm_xen.py | 28 ----------------------------
 10 files changed, 37 insertions(+), 53 deletions(-)



             reply	other threads:[~2025-03-19 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 13:18 Thomas Huth [this message]
2025-03-19 13:18 ` [PULL 1/8] hw/virtio: Also include md stubs in case CONFIG_VIRTIO_PCI is not set Thomas Huth
2025-03-19 13:18 ` [PULL 2/8] tests/functional/test_arm_orangepi: rename test class to 'OrangePiMachine' Thomas Huth
2025-03-19 13:18 ` [PULL 3/8] tests/functional: remove all class level fields Thomas Huth
2025-03-19 13:18 ` [PULL 4/8] docs/system: Use the meson binary from the pyvenv Thomas Huth
2025-03-19 13:18 ` [PULL 5/8] docs/system/arm: Use "functional tests" instead of "integration tests" Thomas Huth
2025-03-19 13:18 ` [PULL 6/8] docs/devel/testing/functional: Add a section about logging Thomas Huth
2025-03-19 13:18 ` [PULL 7/8] tests/functional/test_x86_64_kvm_xen: Remove avocado tags Thomas Huth
2025-03-19 13:18 ` [PULL 8/8] tests/functional/test_migration: Use "ncat" instead of "nc" in the exec test 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=20250319131851.148817-1-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).