From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: [PATCH] arch: *: cpuinfo: harmonize command description
Date: Tue, 27 Nov 2018 09:59:47 +0100 [thread overview]
Message-ID: <6r8t1e99q4.fsf@pengutronix.de> (raw)
In-Reply-To: <20181122183918.e222c20e51c6e41afcfd5d6a@gmail.com>
Hi Antony & Robert,
On Thu, Nov 22 2018 at 14:39 +0100, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> On Thu, 22 Nov 2018 09:12:00 +0100
> Ulrich Ölmann <u.oelmann@pengutronix.de> wrote:
>
> Hello Robert!
>
> AFAIR you are a native English speaker.
>
> Would you please comment this change
>
>> - BAREBOX_CMD_DESC("show CPU information")
>> + BAREBOX_CMD_DESC("show information about CPU")
>
> Which version of the cpuinfo command description is better?
I do not stick to the command description suggested in my patch and in
particular have no preference for one or the other of the above
alternatives - native speakers stand up: advice welcome! ;-)
The motivation for my patch was only the harmonization of things after
accidentally stumbling across different descriptions for the same
command. So perhaps let's harmonize the other commands' descriptions as
well and do it altogether in a v2.
Best regards
Ulrich
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-11-27 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 8:12 Ulrich Ölmann
2018-11-22 15:39 ` Antony Pavlov
2018-11-27 8:59 ` Ulrich Ölmann [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=6r8t1e99q4.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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