From: Shuah Khan <skhan@linuxfoundation.org>
To: Roberto Ricci <io@r-ricci.it>, 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,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v5 2/4] cpupower-frequency-info.1: use the proper name of the --perf option
Date: Tue, 24 Mar 2026 17:11:52 -0600 [thread overview]
Message-ID: <2b20d428-928f-4344-ba11-40356a00f3b4@linuxfoundation.org> (raw)
In-Reply-To: <32cdfa7a-765c-4f74-9839-d2e0b01435dc@linuxfoundation.org>
On 3/24/26 17:06, 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'},
>>
>> Signed-off-by: Roberto Ricci <io@r-ricci.it>
>> ---
>> tools/power/cpupower/man/cpupower-frequency-info.1 | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/power/cpupower/man/cpupower-frequency-info.1 b/tools/power/cpupower/man/cpupower-frequency-info.1
>> index 47fdd7218748..1173d4f31e69 100644
>> --- 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
You can send just this one patch unless there are dependencies with
others.
thanks,
-- Shuah
next prev parent reply other threads:[~2026-03-24 23:11 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 [this message]
2026-03-25 11:25 ` Roberto Ricci
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=2b20d428-928f-4344-ba11-40356a00f3b4@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=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=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
Powered by JetHome