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 3/4] cpupower-frequency-info.1: document --boost and --epp options
Date: Wed, 11 Mar 2026 14:36:38 -0600 [thread overview]
Message-ID: <c3fd1b01-0184-43ef-9739-f523650cb6fb@linuxfoundation.org> (raw)
In-Reply-To: <abHAhAg-6gaK0Qn7@desktop0a>
On 3/11/26 13:20, Roberto Ricci wrote:
Missing change log
> Signed-off-by: Roberto Ricci <io@r-ricci.it>
> ---
> tools/power/cpupower/man/cpupower-frequency-info.1 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/power/cpupower/man/cpupower-frequency-info.1 b/tools/power/cpupower/man/cpupower-frequency-info.1
> index 1173d4f31e69..1dc7536e13ab 100644
> --- a/tools/power/cpupower/man/cpupower-frequency-info.1
> +++ b/tools/power/cpupower/man/cpupower-frequency-info.1
> @@ -32,6 +32,12 @@ Gets the currently used cpufreq policy.
> \fB\-g\fR \fB\-\-governors\fR
> Determines available cpufreq governors.
> .TP
> +\fB\-b\fR \fB\-\-boost\fR
> +Gets the current boost state support.
> +.TP
> +\fB\-z\fR \fB\-\-epp\fR
> +Gets the current EPP (energy performance preference).
> +.TP
> \fB\-r\fR \fB\-\-related\-cpus\fR
> Determines which CPUs run at the same hardware frequency.
> .TP
thanks,
-- Shuah
next prev parent reply other threads:[~2026-03-11 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 19:20 Roberto Ricci
2026-03-11 20:36 ` Shuah Khan [this message]
2026-03-11 23:41 ` [PATCH v2 3/4] cpupower-frequency-info.1: document --boost and --epp 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=c3fd1b01-0184-43ef-9739-f523650cb6fb@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
all inboxes | Powered by JetHome®