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 2/4] cpupower-frequency-info.1: fix long option name
Date: Wed, 11 Mar 2026 14:42:17 -0600 [thread overview]
Message-ID: <d7def94c-bead-4544-9208-97e6f0d07483@linuxfoundation.org> (raw)
In-Reply-To: <abHAdH-ggaxUugCy@desktop0a>
On 3/11/26 13:20, Roberto Ricci wrote:
> The long version of the option is --performance, not --perf.
Okay - I need more than this than the cryptic change log
Include options running the command
>
> 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
> Get performances and frequencies capabilities of CPPC, by reading it from hardware (only available on the hardware with CPPC).
> .TP
> .SH "REMARKS"
thanks,
-- Shuah
next prev parent reply other threads:[~2026-03-11 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 19:20 [PATCH 2/4] cpupower-frequency-info.1: fix long option name Roberto Ricci
2026-03-11 20:42 ` Shuah Khan [this message]
2026-03-11 23:39 ` [PATCH v2 2/4] cpupower-frequency-info.1: use proper name of --perf option Roberto Ricci
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=d7def94c-bead-4544-9208-97e6f0d07483@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