From: "J. Neuschäfer" <j.ne@posteo.net>
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: j.ne@posteo.net, Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: Re: [PATCH 3/3] cmd: ufetch: Show CPU architecture under "CPU"
Date: Mon, 9 Dec 2024 16:58:13 +0000 [thread overview]
Message-ID: <Z1chpQhSV1VdD5W2@probook> (raw)
In-Reply-To: <5bcf5c84-9d45-4ae1-a3b0-613b800101fa@linaro.org>
On Mon, Dec 09, 2024 at 04:09:30PM +0100, Caleb Connolly wrote:
> Thanks for the patch!
>
> On 05/12/2024 19:35, J. Neuschäfer via B4 Relay wrote:
> > From: "J. Neuschäfer" <j.ne@posteo.net>
> >
> > When looking at ufetch output it isn't immediately obvious which CPU
> > architecture the presented board has. This patch therefore adds the CPU
> > architecture string (for example "powerpc") to the "CPU:" line.
>
> It would be nice to have the proper fancy name, but this is an
> improvement nonetheless.
True
> >
> > Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> > ---
[...]
> > - printf("CPU:" RESET " %d (1 in use)\n", n_cpus);
> > + printf("CPU: " RESET CONFIG_SYS_ARCH ", %d (1 in use)\n", n_cpus);
>
> This will read like
>
> CPU: arm 4 (1 in use)
>
> which is a bit hard to parse at a glance. How about
>
> CPU: arm [4 cores]
>
> or some other separator between SYS_ARCH and the core count?
Ah yup, good idea. I also struggled with reading this line as it was;
"4 cores" or similar makes it clear what the number means.
-- jn
prev parent reply other threads:[~2024-12-09 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 18:35 [PATCH 0/3] cmd: ufetch improvements J. Neuschäfer via B4 Relay
2024-12-05 18:35 ` [PATCH 1/3] cmd: ufetch: Fix type mismatch on 32-bit J. Neuschäfer via B4 Relay
2024-12-09 14:58 ` Caleb Connolly
2024-12-05 18:35 ` [PATCH 2/3] cmd: Allow building ufetch without CONFIG_BLK J. Neuschäfer via B4 Relay
2024-12-09 15:04 ` Caleb Connolly
2024-12-09 16:51 ` J. Neuschäfer
2024-12-09 16:55 ` Caleb Connolly
2024-12-05 18:35 ` [PATCH 3/3] cmd: ufetch: Show CPU architecture under "CPU" J. Neuschäfer via B4 Relay
2024-12-09 15:09 ` Caleb Connolly
2024-12-09 16:58 ` J. Neuschäfer [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=Z1chpQhSV1VdD5W2@probook \
--to=j.ne@posteo.net \
--cc=caleb.connolly@linaro.org \
--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