From: Roberto Ricci <io@r-ricci.it>
To: 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
Cc: Roberto Ricci <io@r-ricci.it>
Subject: [PATCH v4 0/6] cpupower: fix various man pages issues
Date: Tue, 24 Mar 2026 02:35:37 +0100 [thread overview]
Message-ID: <20260324013543.4776-1-io@r-ricci.it> (raw)
This patch series fixes a few issues with the cpupower manual pages,
such as missing or incorrect options and trailing whitespace.
Signed-off-by: Roberto Ricci <io@r-ricci.it>
---
Changes in v4:
- Remove Fixes tags from commit messages
- Fix issues reported by scripts/checkpatch.pl
- Add patches to trim whitespace from some files
- Add cover letter
Link to v3: https://lore.kernel.org/linux-pm/20260312102029.14980-1-io@r-ricci.it/
Changes in v3:
- Resend because v2 patches have been incorrectly sent as replies to
individual v1 messages.
Links to v2:
- https://lore.kernel.org/linux-pm/abH7pF9p8KxAsHIE@desktop0a/
- https://lore.kernel.org/linux-pm/abH9KsKbvyi-iceb@desktop0a/
- https://lore.kernel.org/linux-pm/abH9rMVuy8wmzgkG@desktop0a/
- https://lore.kernel.org/linux-pm/abH9_Jk-ckkJvsGb@desktop0a/
Changes in v2:
- More descriptive commit messages
Links to v1:
- https://lore.kernel.org/linux-pm/abHAZj9xwfDf5JVZ@desktop0a/
- https://lore.kernel.org/linux-pm/abHAdH-ggaxUugCy@desktop0a/
- https://lore.kernel.org/linux-pm/abHAhAg-6gaK0Qn7@desktop0a/
- https://lore.kernel.org/linux-pm/abHAkgiPg8VDpDoV@desktop0a/
---
Roberto Ricci (6):
cpupower-frequency-set.1: trim trailing whitespace
cpupower-idle-info.1: fix short option names
cpupower-frequency-info.1: trim trailing whitespace
cpupower-frequency-info.1: use the proper name of the --perf option
cpupower-frequency-info.1: document --boost and --epp options
cpupower-info.1: describe the --perf-bias option
.../cpupower/man/cpupower-frequency-info.1 | 64 ++++++++++---------
.../cpupower/man/cpupower-frequency-set.1 | 42 ++++++------
tools/power/cpupower/man/cpupower-idle-info.1 | 4 +-
tools/power/cpupower/man/cpupower-info.1 | 9 ++-
4 files changed, 66 insertions(+), 53 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-24 1:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 1:35 Roberto Ricci [this message]
2026-03-24 1:35 ` [PATCH v4 1/6] cpupower-frequency-set.1: trim trailing whitespace Roberto Ricci
2026-03-24 19:59 ` Shuah Khan
2026-03-24 22:08 ` Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 2/6] cpupower-idle-info.1: fix short option names Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 3/6] cpupower-frequency-info.1: trim trailing whitespace Roberto Ricci
2026-03-24 20:00 ` Shuah Khan
2026-03-24 22:04 ` Roberto Ricci
2026-03-24 22:09 ` Shuah Khan
2026-03-24 1:35 ` [PATCH v4 4/6] cpupower-frequency-info.1: use the proper name of the --perf option Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 5/6] cpupower-frequency-info.1: document --boost and --epp options Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 6/6] cpupower-info.1: describe the --perf-bias 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=20260324013543.4776-1-io@r-ricci.it \
--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=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®