From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Cc: Junjie Cao <junjie.cao@linux.dev>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [PULL 2/5] hw/m68k/next-cube: Show deprecation notice to users
Date: Mon, 2 Nov 2026 17:30:41 +0100 [thread overview]
Message-ID: <20261102163044.644663-3-thuth@redhat.com> (raw)
In-Reply-To: <20261102163044.644663-1-thuth@redhat.com>
From: Peter Maydell <peter.maydell@linaro.org>
In commit 5d3333e12a034 we deprecated the next-cube machine, but
forgot to set its MachineClass::deprecation_reason. Add that, so
that anybody running the machine is shown the warning that it's
now deprecated.
Fixes: 5d3333e12a034 ("docs/about: Deprecate the 'next-cube' m68k machine")
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-ID: <20261030100659.781819-1-peter.maydell@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
hw/m68k/next-cube.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/m68k/next-cube.c b/hw/m68k/next-cube.c
index d8cb4a8c23d..0d927c7b485 100644
--- a/hw/m68k/next-cube.c
+++ b/hw/m68k/next-cube.c
@@ -1370,6 +1370,7 @@ static void next_machine_class_init(ObjectClass *oc, const void *data)
mc->default_ram_id = "next.ram";
mc->default_cpu_type = M68K_CPU_TYPE_NAME("m68040");
mc->no_cdrom = true;
+ mc->deprecation_reason = "machine is incomplete and cannot boot a kernel";
}
static const TypeInfo next_typeinfo = {
--
2.56.0
next prev parent reply other threads:[~2026-11-02 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:30 [PULL 0/5] Misc patches before the v11.2 softfreeze Thomas Huth
2026-11-02 16:30 ` [PULL 1/5] tests: Add a target to run all tests in thorough mode Thomas Huth
2026-11-02 16:30 ` Thomas Huth [this message]
2026-11-02 16:30 ` [PULL 3/5] usb-host: reset the open retry count after a successful open Thomas Huth
2026-11-02 16:30 ` [PULL 4/5] hw/usb/hcd-xhci: fail Address Device when the DCBAA entry is unreadable Thomas Huth
2026-11-02 16:30 ` [PULL 5/5] tests/qtest/usb-hcd-xhci: test Address Device with an unreadable DCBAA Thomas Huth
2026-11-03 15:24 ` [PULL 0/5] Misc patches before the v11.2 softfreeze Richard Henderson
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=20261102163044.644663-3-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=junjie.cao@linux.dev \
--cc=peter.maydell@linaro.org \
--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 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.