Removed trailing white space at end of lines

man2/getcpu.2

@@ -103,7 +103,7 @@ migrating threads between CPUs, and so the argument is now ignored.
 .\" The information inside the cache is private to the system call
 .\" and should not be accessed by the user program.
 .\" The information placed in the cache can change between kernel releases.
-.\" 
+.\"
 .\" When no cache is specified
 .\" .BR getcpu ()
 .\" will be slower,

man7/cpuset.7

@@ -280,7 +280,7 @@ See the \fBMemory Migration\fR section, below.
 A measure of how much memory pressure the processes in this
 cpuset are causing.
 See the \fBMemory Pressure\fR section, below.
-Unless 
+Unless
 .I memory_pressure_enabled
 is enabled, always has value zero (0).
 This file is read-only.
@@ -291,9 +291,9 @@ section, below.
 .TP
 .IR memory_pressure_enabled " (since Linux 2.6.16)"
 Flag (0 or 1).
-This file is only present in the root cpuset, normally 
+This file is only present in the root cpuset, normally
 .IR /dev/cpuset .
-If set (1), the 
+If set (1), the
 .I memory_pressure
 calculations are enabled for all cpusets in the system.
 By default this is off (0).
@@ -388,7 +388,7 @@ The "allowed" fields were addded in Linux 2.6.24;
 the "allowed_list" fields were added in Linux 2.6.26.
 .\" ================== EXTENDED CAPABILITIES ==================
 .SH EXTENDED CAPABILITIES
-In addition to controlling which 
+In addition to controlling which
 .I cpus
 and
 .I mems
@@ -436,7 +436,7 @@ or
 set is a
 .I hardwall
 cpuset.
-A 
+A
 .I hardwall
 cpuset restricts kernel allocations for page, buffer,
 and other data commonly shared by the kernel across multiple users.
@@ -461,7 +461,7 @@ interrupt handlers, is allowed to be taken outside even a
 cpuset.
 .\" ================== Notify On Release ==================
 .SS Notify On Release
-If the 
+If the
 .I notify_on_release
 flag is enabled (1) in a cpuset,
 then whenever the last process in the cpuset leaves
@@ -582,7 +582,7 @@ times 1000.
 There are two Boolean flag files per cpuset that control where the
 kernel allocates pages for the file-system buffers and related
 in-kernel data structures.
-They are called 
+They are called
 .I memory_spread_page
 and
 .IR memory_spread_slab .
@@ -789,7 +789,7 @@ balancing off the software clock described in
 The setting of
 .I sched_relax_domain_level
 only applies to immediate load balancing.
-Regardless of the 
+Regardless of the
 .I sched_relax_domain_level
 setting, periodic load balancing is attempted over all CPUs
 (unless disabled by turning off
@@ -845,7 +845,7 @@ hence that load balancing is only done periodically,
 not immediately when a CPU becomes available or another task becomes
 runnable.
 .PP
-The 
+The
 .I sched_relax_domain_level
 value of minus one (\-1)
 always means use the system default value.
@@ -939,7 +939,7 @@ if its parent is.
 If it is
 .IR cpu_exclusive ,
 its CPUs may not overlap any sibling.
-.IP * 
+.IP *
 If it is
 .IR memory_exclusive ,
 its memory nodes may not overlap any sibling.
@@ -947,7 +947,7 @@ its memory nodes may not overlap any sibling.
 .SH PERMISSIONS
 The permissions of a cpuset are determined by the permissions
 of the directories and pseudo-files in the cpuset file system,
-normally mounted at 
+normally mounted at
 .IR /dev/cpuset .
 .PP
 For instance, a process can put itself in some other cpuset (than
@@ -992,7 +992,7 @@ if either the process's current working directory is its cpuset
 .B cd
 or
 .BR chdir (2)
-to its cpuset directory beneath 
+to its cpuset directory beneath
 .IR /dev/cpuset ,
 which is a bit unusual)
 or if some user code converts the relative cpuset path to a