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: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 0/5] Sparc CPU naming and help text improvements
Date: Mon, 15 Apr 2024 09:26:49 +0200 [thread overview]
Message-ID: <bdd66aac-4de5-44a1-a1d1-86825d337d12@redhat.com> (raw)
In-Reply-To: <20240307174334.130407-1-thuth@redhat.com>
On 07/03/2024 18.43, Thomas Huth wrote:
> The Sparc CPU naming and the corresponding help text is somewhat
> confusing for the users. We should avoid spaces in the Names and
> provide clear information to the users what can be passed to the
> "-cpu" option.
> While we're at it, also remove the "+" from two of the CPU names
> since this character is now not allowed in device names anymore
> (and was worked around with an ugly hack in qom/object.c so far).
>
> Thomas Huth (5):
> target/sparc/cpu: Rename the CPU models with a "+" in their names
> target/sparc/cpu: Avoid spaces by default in the CPU names
> target/sparc/cpu: Improve the CPU help text
> docs/system/target-sparc: Improve the Sparc documentation
> docs/about: Deprecate the old "UltraSparc" CPU names that contain a
> "+"
Ping!
Mark, Aryom, could you please comment on this patch series, too?
Thanks,
Thomas
next prev parent reply other threads:[~2024-04-15 7:28 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 ` [PATCH 5/5] docs/about: Deprecate the old "UltraSparc" CPU names that contain a "+" Thomas Huth
2024-04-18 20:28 ` Mark Cave-Ayland
2024-04-15 7:26 ` Thomas Huth [this message]
2024-04-18 20:08 ` [PATCH 0/5] Sparc CPU naming and help text improvements 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=bdd66aac-4de5-44a1-a1d1-86825d337d12@redhat.com \
--to=thuth@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=berrange@redhat.com \
--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).