public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: alison.wang@nxp.com, angelo@kernel-space.org, trini@konsulko.com
Cc: me@ziyao.cc, daniel@0x0f.com, heinrich.schuchardt@canonical.com,
	jserv@ccns.ncku.edu.tw, eleanor15x@gmail.com,
	u-boot@lists.denx.de, Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [PATCH v4 6/6] CI: Add test jobs for QEMU m68k virt machine
Date: Thu,  1 Jan 2026 17:54:20 +0000	[thread overview]
Message-ID: <20260101175420.4118024-7-visitorckw@gmail.com> (raw)
In-Reply-To: <20260101175420.4118024-1-visitorckw@gmail.com>

Enable CI testing for the newly introduced QEMU m68k 'virt' board on
both GitLab CI and Azure Pipelines. This ensures the new M68040
architecture support is built and booted correctly in the emulated
environment.

Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
---
No changes in v4.

 .azure-pipelines.yml | 3 +++
 .gitlab-ci.yml       | 6 ++++++
 2 files changed, 9 insertions(+)

diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index e4695f1c55b..f563878b021 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -518,6 +518,9 @@ stages:
           TEST_PY_ID: "--id qemu"
           TEST_PY_TEST_SPEC: "not sleep and not efi"
           OVERRIDE: "-a CONFIG_M68K_QEMU=y -a ~CONFIG_MCFTMR"
+        qemu_m68k_virt:
+          TEST_PY_BD: "qemu-m68k"
+          TEST_PY_TEST_SPEC: "not sleep"
         qemu_malta:
           TEST_PY_BD: "malta"
           TEST_PY_ID: "--id qemu"
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index e7234e003ea..1fc4d1e656d 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -408,6 +408,12 @@ qemu_m68k test.py:
     OVERRIDE: "-a CONFIG_M68K_QEMU=y -a ~CONFIG_MCFTMR"
   <<: *buildman_and_testpy_dfn
 
+qemu_m68k_virt test.py:
+  variables:
+    TEST_PY_BD: "qemu-m68k"
+    TEST_PY_TEST_SPEC: "not sleep"
+  <<: *buildman_and_testpy_dfn
+
 qemu_malta test.py:
   variables:
     TEST_PY_BD: "malta"
-- 
2.52.0.358.g0dd7633a29-goog


      parent reply	other threads:[~2026-01-01 21:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-01 17:54 [PATCH v4 0/6] m68k: Add support for QEMU virt machine Kuan-Wei Chiu
2026-01-01 17:54 ` [PATCH v4 1/6] serial: Add Goldfish TTY driver Kuan-Wei Chiu
2026-01-02  8:29   ` Heinrich Schuchardt
2026-01-02  8:40     ` Heinrich Schuchardt
2026-01-02 21:48       ` Kuan-Wei Chiu
2026-01-02 21:51         ` Tom Rini
2026-01-02 23:14           ` Kuan-Wei Chiu
2026-01-05 14:43             ` Tom Rini
2026-01-05 15:44               ` Kuan-Wei Chiu
2026-01-01 17:54 ` [PATCH v4 2/6] timer: Add Goldfish timer driver Kuan-Wei Chiu
2026-01-01 17:54 ` [PATCH v4 3/6] rtc: goldfish: Support platform data for non-DT probing Kuan-Wei Chiu
2026-01-02  8:27   ` Heinrich Schuchardt
2026-01-01 17:54 ` [PATCH v4 4/6] m68k: Add support for M68040 CPU Kuan-Wei Chiu
2026-01-01 17:54 ` [PATCH v4 5/6] board: Add QEMU m68k virt board support Kuan-Wei Chiu
2026-01-02  9:26   ` Heinrich Schuchardt
2026-01-02 21:46     ` Kuan-Wei Chiu
2026-01-01 17:54 ` Kuan-Wei Chiu [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=20260101175420.4118024-7-visitorckw@gmail.com \
    --to=visitorckw@gmail.com \
    --cc=alison.wang@nxp.com \
    --cc=angelo@kernel-space.org \
    --cc=daniel@0x0f.com \
    --cc=eleanor15x@gmail.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=me@ziyao.cc \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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