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 v3 4/4] cpupower-info.1: describe the --perf-bias option
Date: Mon, 23 Mar 2026 12:34:12 -0600 [thread overview]
Message-ID: <e41be58d-88de-40ce-aa6e-c4d1febe2270@linuxfoundation.org> (raw)
In-Reply-To: <20260312102029.14980-4-io@r-ricci.it>
On 3/12/26 04:20, Roberto Ricci wrote:
> The cpupower-info(1) man page only mentions the short form of the
> '--perf-bias' option in the synopsys, but the long form is not
> documented and its effect is not explained.
>
> Fixes 7fe2f6399a84760a9af8896ac152728250f82adb ("cpupowerutils - cpufrequtils extended with quite some features")
>
> Signed-off-by: Roberto Ricci <io@r-ricci.it>
Remove Fixes tag from all these 4 patches and run checkpatch
before sending patches to me adding version information.
+ add a cover letter is helpful and makes it easier to comment
on things common across all patches such as these.
thanks,
-- Shuah
next prev parent reply other threads:[~2026-03-23 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 10:20 [PATCH v3 1/4] cpupower-idle-info.1: fix short option names Roberto Ricci
2026-03-12 10:20 ` [PATCH v3 2/4] cpupower-frequency-info.1: use the proper name of the --perf option Roberto Ricci
2026-03-23 18:32 ` Shuah Khan
2026-03-12 10:20 ` [PATCH v3 3/4] cpupower-frequency-info.1: document --boost and --epp options Roberto Ricci
2026-03-23 18:34 ` Shuah Khan
2026-03-12 10:20 ` [PATCH v3 4/4] cpupower-info.1: describe the --perf-bias option Roberto Ricci
2026-03-23 18:34 ` Shuah Khan [this message]
2026-03-23 18:31 ` [PATCH v3 1/4] cpupower-idle-info.1: fix short option names 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=e41be58d-88de-40ce-aa6e-c4d1febe2270@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