Remove useless spaces at the end of some lines in
cpupower-frequency-info.1.

Signed-off-by: Roberto Ricci <io@r-ricci.it>
---
 .../cpupower/man/cpupower-frequency-info.1    | 56 +++++++++----------
 1 file changed, 28 insertions(+), 28 deletions(-)

diff --git a/tools/power/cpupower/man/cpupower-frequency-info.1 b/tools/power/cpupower/man/cpupower-frequency-info.1
index 47fdd7218748..e4173417b7c6 100644
--- a/tools/power/cpupower/man/cpupower-frequency-info.1
+++ b/tools/power/cpupower/man/cpupower-frequency-info.1
@@ -1,80 +1,80 @@
 .TH "CPUPOWER\-FREQUENCY\-INFO" "1" "0.1" "" "cpupower Manual"
 .SH "NAME"
-.LP 
+.LP
 cpupower\-frequency\-info \- Utility to retrieve cpufreq kernel information
 .SH "SYNTAX"
-.LP 
+.LP
 cpupower [ \-c cpulist ] frequency\-info [\fIoptions\fP]
 .SH "DESCRIPTION"
-.LP 
+.LP
 A small tool which prints out cpufreq information helpful to developers and interested users.
 .SH "OPTIONS"
-.LP 
-.TP  
+.LP
+.TP
 \fB\-e\fR \fB\-\-debug\fR
 Prints out debug information.
-.TP  
+.TP
 \fB\-f\fR \fB\-\-freq\fR
 Get frequency the CPU currently runs at, according to the cpufreq core.
-.TP  
+.TP
 \fB\-w\fR \fB\-\-hwfreq\fR
 Get frequency the CPU currently runs at, by reading it from hardware (only available to root).
-.TP  
+.TP
 \fB\-l\fR \fB\-\-hwlimits\fR
 Determine the minimum and maximum CPU frequency allowed.
-.TP  
+.TP
 \fB\-d\fR \fB\-\-driver\fR
 Determines the used cpufreq kernel driver.
-.TP  
+.TP
 \fB\-p\fR \fB\-\-policy\fR
 Gets the currently used cpufreq policy.
-.TP  
+.TP
 \fB\-g\fR \fB\-\-governors\fR
 Determines available cpufreq governors.
-.TP  
+.TP
 \fB\-r\fR \fB\-\-related\-cpus\fR
 Determines which CPUs run at the same hardware frequency.
-.TP  
+.TP
 \fB\-a\fR \fB\-\-affected\-cpus\fR
 Determines which CPUs need to have their frequency coordinated by software.
-.TP  
+.TP
 \fB\-s\fR \fB\-\-stats\fR
 Shows cpufreq statistics if available.
-.TP  
+.TP
 \fB\-y\fR \fB\-\-latency\fR
 Determines the maximum latency on CPU frequency changes.
-.TP  
+.TP
 \fB\-o\fR \fB\-\-proc\fR
 Prints out information like provided by the /proc/cpufreq interface in 2.4. and early 2.6. kernels.
-.TP  
+.TP
 \fB\-m\fR \fB\-\-human\fR
 human\-readable output for the \-f, \-w, \-s and \-y parameters.
-.TP  
+.TP
 \fB\-n\fR \fB\-\-no-rounding\fR
 Output frequencies and latencies without rounding off values.
-.TP  
+.TP
 \fB\-c\fR \fB\-\-perf\fR
 Get performances and frequencies capabilities of CPPC, by reading it from hardware (only available on the hardware with CPPC).
 .TP
 .SH "REMARKS"
-.LP 
+.LP
 By default only values of core zero are displayed. How to display settings of
 other cores is described in the cpupower(1) manpage in the \-\-cpu option section.
-.LP 
+.LP
 You can't specify more than one of the output specific options \-o \-e \-a \-g \-p \-d \-l \-w \-f \-y.
-.LP 
+.LP
 You also can't specify the \-o option combined with the \-c option.
 .SH "FILES"
-.nf 
-\fI/sys/devices/system/cpu/cpu*/cpufreq/\fP  
-\fI/proc/cpufreq\fP (deprecated) 
+.nf
+\fI/sys/devices/system/cpu/cpu*/cpufreq/\fP
+\fI/proc/cpufreq\fP (deprecated)
 \fI/proc/sys/cpu/\fP (deprecated)
-.fi 
+.fi
 .SH "AUTHORS"
 .nf
-Dominik Brodowski <linux@brodo.de> \- author 
+Dominik Brodowski <linux@brodo.de> \- author
 Mattia Dongili<malattia@gmail.com> \- first autolibtoolization
 .fi
 .SH "SEE ALSO"
-.LP 
+.LP
 cpupower\-frequency\-set(1), cpupower(1)
-- 
2.53.0

On 3/23/26 19:35, Roberto Ricci wrote:
> Remove useless spaces at the end of some lines in
> cpupower-frequency-info.1.
> 

Why are the spaces useless and what happens if you don't
remove them?

thanks,
-- Shuah

On 2026-03-24 14:00 -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-info.1.
> 
> Why are the spaces useless and what happens if you don't
> remove them?

They seem to be both useless and harmless. With or without trailing
spaces, the output is identical (tested with both mandoc and groff).
Since I added the new options by copy-pasting the existing ones and
changing the text, my patch added lines with trailing whitespace and
checkpatch.pl complained about this. Removing these spaces from just the
new lines fixes the error, but I decided to remove them from all the
lines in the file for consistency.

On 3/24/26 16:04, Roberto Ricci wrote:
> On 2026-03-24 14:00 -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-info.1.
>>
>> Why are the spaces useless and what happens if you don't
>> remove them?
> 
> They seem to be both useless and harmless. With or without trailing
> spaces, the output is identical (tested with both mandoc and groff).
> Since I added the new options by copy-pasting the existing ones and
> changing the text, my patch added lines with trailing whitespace and
> checkpatch.pl complained about this. Removing these spaces from just the
> new lines fixes the error, but I decided to remove them from all the
> lines in the file for consistency.

Right - I ran these through mandoc - Since they don't change anything,
I would rather not take these whitespace removal patches.

Is there a dependency between the whitespace ones and the other patches?
Can you drop the whitespace ones and send me just the fix patches?

thanks,
-- Shuah