qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Artyom Tarasenko <atar4qemu@gmail.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "Eduardo Habkost" <eduardo@habkost.net>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [PATCH 5/5] docs/about: Deprecate the old "UltraSparc" CPU names that contain a "+"
Date: Thu,  7 Mar 2024 18:43:34 +0100	[thread overview]
Message-ID: <20240307174334.130407-6-thuth@redhat.com> (raw)
In-Reply-To: <20240307174334.130407-1-thuth@redhat.com>

For consistency we should drop the names with a "+" in it in the
long run.

Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 docs/about/deprecated.rst | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
index 8565644da6..7058341f8f 100644
--- a/docs/about/deprecated.rst
+++ b/docs/about/deprecated.rst
@@ -202,6 +202,15 @@ in the QEMU object model anymore. ``power5+``, ``power5+_v2.1``,
 an alias, but for consistency these will get removed in a future
 release, too. Use ``power5p_v2.1`` and ``power7p_v2.1`` instead.
 
+``Sun-UltraSparc-IIIi+`` and ``Sun-UltraSparc-IV+`` CPU names (since 9.0)
+'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+The character "+" in device (and thus also CPU) names is not allowed
+in the QEMU object model anymore. ``Sun-UltraSparc-IIIi+`` and
+``Sun-UltraSparc-IV+`` are currently still supported via a workaround,
+but for consistency these will get removed in a future release, too.
+Use ``Sun-UltraSparc-IIIip`` and ``Sun-UltraSparc-IVp`` instead.
+
 CRIS CPU architecture (since 9.0)
 '''''''''''''''''''''''''''''''''
 
-- 
2.44.0



  parent reply	other threads:[~2024-03-07 17:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 17:43 [PATCH 0/5] Sparc CPU naming and help text improvements Thomas Huth
2024-03-07 17:43 ` [PATCH 1/5] target/sparc/cpu: Rename the CPU models with a "+" in their names Thomas Huth
2024-03-07 21:22   ` Richard Henderson
2024-03-08  5:12     ` Thomas Huth
2024-04-18 20:03   ` Mark Cave-Ayland
2024-03-07 17:43 ` [PATCH 2/5] target/sparc/cpu: Avoid spaces by default in the CPU names Thomas Huth
2024-03-07 21:28   ` Richard Henderson
2024-04-18 20:05   ` Mark Cave-Ayland
2024-03-07 17:43 ` [PATCH 3/5] target/sparc/cpu: Improve the CPU help text Thomas Huth
2024-03-07 18:46   ` Philippe Mathieu-Daudé
2024-03-07 21:31   ` Richard Henderson
2024-03-07 17:43 ` [PATCH 4/5] docs/system/target-sparc: Improve the Sparc documentation Thomas Huth
2024-04-18 20:27   ` Mark Cave-Ayland
2024-04-19  4:59     ` Thomas Huth
2024-04-19  5:38       ` Mark Cave-Ayland
2024-04-19 23:14     ` Brad Smith
2024-04-20  5:44       ` Mark Cave-Ayland
2024-03-07 17:43 ` Thomas Huth [this message]
2024-04-18 20:28   ` [PATCH 5/5] docs/about: Deprecate the old "UltraSparc" CPU names that contain a "+" Mark Cave-Ayland
2024-04-15  7:26 ` [PATCH 0/5] Sparc CPU naming and help text improvements Thomas Huth
2024-04-18 20:08   ` Mark Cave-Ayland
2024-04-18 20:30     ` Mark Cave-Ayland

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=20240307174334.130407-6-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=atar4qemu@gmail.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).