qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 19/24] tests/functional: Move s390x tests into target-specific folders
Date: Mon, 4 Aug 2025 10:34:04 +0200	[thread overview]
Message-ID: <39cbef79-1412-4076-a43f-6392a76e29ea@linaro.org> (raw)
In-Reply-To: <20250801151251.751368-20-thuth@redhat.com>

On 1/8/25 17:12, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
> 
> The tests/functional folder has become quite crowded, thus move the
> s390x tests into a target-specific subfolder.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>   MAINTAINERS                                         |  6 +++---
>   tests/functional/meson.build                        | 13 +------------
>   tests/functional/s390x/meson.build                  | 13 +++++++++++++
>   .../test_ccw_virtio.py}                             |  0
>   .../test_pxelinux.py}                               |  0
>   .../{test_s390x_replay.py => s390x/test_replay.py}  |  0
>   .../test_topology.py}                               |  0
>   .../{test_s390x_tuxrun.py => s390x/test_tuxrun.py}  |  0
>   8 files changed, 17 insertions(+), 15 deletions(-)
>   create mode 100644 tests/functional/s390x/meson.build
>   rename tests/functional/{test_s390x_ccw_virtio.py => s390x/test_ccw_virtio.py} (100%)
>   rename tests/functional/{test_s390x_pxelinux.py => s390x/test_pxelinux.py} (100%)
>   rename tests/functional/{test_s390x_replay.py => s390x/test_replay.py} (100%)
>   rename tests/functional/{test_s390x_topology.py => s390x/test_topology.py} (100%)
>   rename tests/functional/{test_s390x_tuxrun.py => s390x/test_tuxrun.py} (100%)

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>



  reply	other threads:[~2025-08-04  8:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01 15:12 [PATCH 00/24] tests/functional: Move tests into architecture specific folders Thomas Huth
2025-08-01 15:12 ` [PATCH 01/24] tests/functional: Rework the migration test to have target-specific files Thomas Huth
2025-08-01 15:12 ` [PATCH 02/24] tests/functional: Rework the multiprocess " Thomas Huth
2025-08-01 15:12 ` [PATCH 03/24] tests/functional/meson.build: Split timeout settings by target Thomas Huth
2025-08-01 15:12 ` [PATCH 04/24] tests/functional/meson.build: Allow tests to reside in subfolders Thomas Huth
2025-08-01 15:12 ` [PATCH 05/24] tests/functional: Move aarch64 tests into architecture specific folder Thomas Huth
2025-08-01 15:12 ` [PATCH 06/24] tests/functional: Move alpha " Thomas Huth
2025-08-04  8:35   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 07/24] tests/functional: Move arm " Thomas Huth
2025-08-04 12:28   ` Cédric Le Goater
2025-08-05 13:58     ` Thomas Huth
2025-08-01 15:12 ` [PATCH 08/24] tests/functional: Move avr " Thomas Huth
2025-08-04  8:38   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 09/24] tests/functional: Move hppa " Thomas Huth
2025-08-04  8:34   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 10/24] tests/functional: Move i386 " Thomas Huth
2025-08-01 15:12 ` [PATCH 11/24] tests/functional: Move loongarch64 " Thomas Huth
2025-08-04  8:36   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 12/24] tests/functional: Move m68k " Thomas Huth
2025-08-04  8:34   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 13/24] tests/functional: Move microblaze " Thomas Huth
2025-08-06  7:13   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 14/24] tests/functional: Move mips tests into target-specific folders Thomas Huth
2025-08-04  8:31   ` Philippe Mathieu-Daudé
2025-08-05 13:56     ` Thomas Huth
2025-08-06  7:11       ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 15/24] tests/functional: Move or1k " Thomas Huth
2025-08-04  8:36   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 16/24] tests/functional: Move ppc/ppc64 " Thomas Huth
2025-08-01 15:12 ` [PATCH 17/24] tests/functional: Move riscv32/riscv64 " Thomas Huth
2025-08-04  8:37   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 18/24] tests/functional: Move rx test " Thomas Huth
2025-08-04  8:32   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 19/24] tests/functional: Move s390x tests " Thomas Huth
2025-08-04  8:34   ` Philippe Mathieu-Daudé [this message]
2025-08-01 15:12 ` [PATCH 20/24] tests/functional: Move sh4/sh4eb " Thomas Huth
2025-08-04  8:33   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 21/24] tests/functional: Move sparc/sparc64 " Thomas Huth
2025-08-04  8:38   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 22/24] tests/functional: Move x86_64 tests into target-specific folder Thomas Huth
2025-08-01 15:12 ` [PATCH 23/24] tests/functional: Move xtensa " Thomas Huth
2025-08-04  8:33   ` Philippe Mathieu-Daudé
2025-08-01 15:12 ` [PATCH 24/24] tests/functional: Move the generic tests to a subfolder Thomas Huth
2025-08-01 20:52 ` [PATCH 00/24] tests/functional: Move tests into architecture specific folders 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=39cbef79-1412-4076-a43f-6392a76e29ea@linaro.org \
    --to=philmd@linaro.org \
    --cc=berrange@redhat.com \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@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).