From: Sascha Hauer <s.hauer@pengutronix.de>
To: Yann Sionneau <ysionneau@kalrayinc.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] sandbox: add cpuinfo command
Date: Fri, 18 Oct 2024 11:06:19 +0200 [thread overview]
Message-ID: <ZxIlC-56_P6aHIrg@pengutronix.de> (raw)
In-Reply-To: <777ad095-34c5-43fd-bd52-a7ca938adcf6@kalrayinc.com>
On Wed, Oct 16, 2024 at 11:32:40AM +0200, Yann Sionneau wrote:
> Hi Ahmad,
>
> On 16/10/2024 10:55, Ahmad Fatoum wrote:
> > We have stack dump support in sandbox via AddressSanitizer, if it's
> > compiled in. To make it easier to test proper operation, let's a cpuinfo
> Small typo in the commit msg
> > command like we already do on ARM and give it the same -s option.
> >
> > Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> > ---
> >
> > +BAREBOX_CMD_START(cpuinfo)
> > + .cmd = do_cpuinfo,
> > + BAREBOX_CMD_DESC("show info about CPU")
> > + BAREBOX_CMD_OPTS("[-s]")
>
> It seems the -s option here is mandatory, maybe remove the [ ] brackets? Not sure if it means "optional" here...
The ARM cpuinfo command shows information about the CPU when called
without options, so on ARM -s is really optional and I think Ahmad
wanted the same behaviour here. It's a bit unfortunate that the sandbox
command doesn't have any information to show when called without
options.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-10-18 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:55 [PATCH 1/2] sandbox: add --command line support Ahmad Fatoum
2024-10-16 8:55 ` [PATCH 2/2] sandbox: add cpuinfo command Ahmad Fatoum
2024-10-16 9:32 ` Yann Sionneau
2024-10-18 9:06 ` Sascha Hauer [this message]
2024-10-21 7:35 ` Ahmad Fatoum
2024-10-16 9:54 ` [PATCH 1/2] sandbox: add --command line support Yann Sionneau
2024-10-16 9:56 ` Ahmad Fatoum
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=ZxIlC-56_P6aHIrg@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ysionneau@kalrayinc.com \
/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