From: Roberto Ricci <io@r-ricci.it>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
"John B. Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/4] cpupower-frequency-info.1: use the proper name of the --perf option
Date: Wed, 25 Mar 2026 12:25:06 +0100 [thread overview]
Message-ID: <acPGEsTIpbPX0uem@desktop0a> (raw)
In-Reply-To: <32cdfa7a-765c-4f74-9839-d2e0b01435dc@linuxfoundation.org>
On 2026-03-24 17:06 -0600, Shuah Khan wrote:
> On 3/24/26 16:39, Roberto Ricci wrote:
> > The cpupower-frequency-info(1) man page describes a '--perf' option.
> > Even though this form is accepted by the program, its proper name is
> > '--performance'.
> >
> > cpufreq-info.c:
> > {"performance", no_argument, NULL, 'c'},
> > [...]
> > --- a/tools/power/cpupower/man/cpupower-frequency-info.1
> > +++ b/tools/power/cpupower/man/cpupower-frequency-info.1
> > @@ -53,7 +53,7 @@ human\-readable output for the \-f, \-w, \-s and \-y parameters.
> > \fB\-n\fR \fB\-\-no-rounding\fR
> > Output frequencies and latencies without rounding off values.
> > .TP
> > -\fB\-c\fR \fB\-\-perf\fR
> > +\fB\-c\fR \fB\-\-performance\fR
>
> I would keep perf and also add performance since --perf and --performance
> work - it is lot easier to type --perf
--perf would still be accepted by the program, whether or not the man
page mentions it. getopt_long() accepts any abbreviation which is not
ambiguous. While I agree that it would be nice to remind users about
abbreviations, why should the man page suggest an arbitrary one out of
the many accepted? And what about the other options (such as
--governors)? Suggesting an abbreviated long form only for --performance
would be inconsistent. The general convention is to list the one-letter
form and the complete long form. Also, if you want to save typing during
interactive use, you can use -c.
next prev parent reply other threads:[~2026-03-25 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 22:39 [PATCH v5 0/4] cpupower: fix various man pages issues Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 1/4] cpupower-idle-info.1: fix short option names Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 2/4] cpupower-frequency-info.1: use the proper name of the --perf option Roberto Ricci
2026-03-24 23:06 ` Shuah Khan
2026-03-24 23:11 ` Shuah Khan
2026-03-25 11:25 ` Roberto Ricci [this message]
2026-03-24 22:39 ` [PATCH v5 3/4] cpupower-frequency-info.1: document --boost and --epp options Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 4/4] cpupower-info.1: describe the --perf-bias option Roberto Ricci
2026-03-25 19:39 ` [PATCH v5 0/4] cpupower: fix various man pages issues Shuah Khan
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=acPGEsTIpbPX0uem@desktop0a \
--to=io@r-ricci.it \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=trenn@suse.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