From: Roberto Ricci <io@r-ricci.it>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Thomas Renninger <trenn@suse.com>,
"John B. Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/6] cpupower-frequency-set.1: trim trailing whitespace
Date: Tue, 24 Mar 2026 23:08:51 +0100 [thread overview]
Message-ID: <acMLc8HX35YyVlWz@desktop0a> (raw)
In-Reply-To: <1c76b560-c40f-4069-b056-c4addc33f470@linuxfoundation.org>
On 2026-03-24 13:59 -0600, Shuah Khan wrote:
> On 3/23/26 19:35, Roberto Ricci wrote:
> > Remove useless spaces at the end of some lines in cpupower-frequency-set.1.
>
> Why are the spaces useless and what happens if you don't
> remove them?
The trailing spaces seem to be both useless and harmless, since the
output is identical regardless of their presence. I trimmed them from
cpupower-frequency-set.1 for consistency with cpupower-frequency-info.1.
See also my reply to your question about patch 3/6 in this series.
next prev parent reply other threads:[~2026-03-24 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 1:35 [PATCH v4 0/6] cpupower: fix various man pages issues Roberto Ricci
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 [this message]
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=acMLc8HX35YyVlWz@desktop0a \
--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=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.