Removed trailing white space at end of lines

man2/bdflush.2

@@ -41,7 +41,7 @@ Since Linux 2.6,
 .\" As noted in a changes in the 2.5.12 source
 this system call is deprecated and does nothing.
 It is likely to disappear altogether in a future kernel release.
-Nowadays, the task performed by 
+Nowadays, the task performed by
 .BR bdflush ()
 is handled by the kernel
 .I pdflush

man2/ptrace.2

@@ -190,7 +190,7 @@ to the address
 .I addr
 in the tracee's memory.
 As for
-.BR PTRACE_PEEKTEXT 
+.BR PTRACE_PEEKTEXT
 and
 .BR PTRACE_PEEKDATA ,
 these two requests are currently equivalent.
@@ -618,7 +618,7 @@ in a multithreaded process.
 The tracer cannot assume that the ptrace-stopped tracee exists.
 There are many scenarios when the tracee may die while stopped (such as
 .BR SIGKILL ).
-Therefore, the tracer must be prepared to handle an 
+Therefore, the tracer must be prepared to handle an
 .B ESRCH
 error on any ptrace operation.
 Unfortunately, the same error is returned if the tracee
@@ -866,7 +866,7 @@ In Linux 2.4 and earlier, the
 signal can't be injected.
 .\" In the Linux 2.4 sources, in arch/i386/kernel/signal.c::do_signal(),
 .\" there is:
-.\" 
+.\"
 .\"             /* The debugger continued.  Ignore SIGSTOP.  */
 .\"             if (signr == SIGSTOP)
 .\"                     continue;
@@ -1182,7 +1182,7 @@ or
 .SS PTRACE_SINGLESTEP, PTRACE_SYSEMU, PTRACE_SYSEMU_SINGLESTEP stops
 [Details of these kinds of stops are yet to be documented.]
 .\"
-.\" FIXME 
+.\" FIXME
 .\" document stops occurring with PTRACE_SINGLESTEP, PTRACE_SYSEMU,
 .\" PTRACE_SYSEMU_SINGLESTEP
 .SS Informational and restarting ptrace commands
@@ -1224,7 +1224,7 @@ is not documented as returning a meaningful event message.
 The call
 
     ptrace(PTRACE_SETOPTIONS, pid, 0, PTRACE_O_flags);
-    
+
 affects one tracee.
 The tracee's current flags are replaced.
 Flags are inherited by new tracees created and "auto-attached" via active
@@ -1309,7 +1309,7 @@ with
 and allow the parent (which is our tracer now) to observe our
 signal-delivery-stop.
 .LP
-If the 
+If the
 .BR PTRACE_O_TRACEFORK ,
 .BR PTRACE_O_TRACEVFORK ,
 or
@@ -1380,7 +1380,7 @@ the pending signal is injected.
 .\" clone(2) THREAD_CLONE says:
 .\"     If  any  of the threads in a thread group performs an execve(2),
 .\"     then all threads other than the thread group leader are terminated,
-.\"     and the new program is executed in the thread group leader.  
+.\"     and the new program is executed in the thread group leader.
 .\"
 When one thread in a multithreaded process calls
 .BR execve (2),
@@ -1534,7 +1534,7 @@ signal to the user, and would suppress its delivery to the tracee (if
 is set to
 .BR SIG_DFL ,
 it is a killing signal).
-However, determining 
+However, determining
 .I which
 .B SIGTRAP
 to suppress is not easy.