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 3/5] target/sparc/cpu: Improve the CPU help text
Date: Thu,  7 Mar 2024 18:43:32 +0100	[thread overview]
Message-ID: <20240307174334.130407-4-thuth@redhat.com> (raw)
In-Reply-To: <20240307174334.130407-1-thuth@redhat.com>

Remove the unnecessary "Sparc" at the beginning of the line and
put the chip information into parentheses so that it is clearer
which part of the line have to be passed to "-cpu" to specify a
different CPU.

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2141
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 target/sparc/cpu.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/target/sparc/cpu.c b/target/sparc/cpu.c
index ae30cded22..6650248ffe 100644
--- a/target/sparc/cpu.c
+++ b/target/sparc/cpu.c
@@ -576,9 +576,10 @@ void sparc_cpu_list(void)
 {
     unsigned int i;
 
+    qemu_printf("Available CPU types:\n");
     for (i = 0; i < ARRAY_SIZE(sparc_defs); i++) {
-        qemu_printf("Sparc %16s IU " TARGET_FMT_lx
-                    " FPU %08x MMU %08x NWINS %d ",
+        qemu_printf(" %-20s (IU " TARGET_FMT_lx
+                    " FPU %08x MMU %08x NWINS %d) ",
                     sparc_defs[i].name,
                     sparc_defs[i].iu_version,
                     sparc_defs[i].fpu_version,
-- 
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 ` Thomas Huth [this message]
2024-03-07 18:46   ` [PATCH 3/5] target/sparc/cpu: Improve the CPU help text 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 ` [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-4-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).