Module Name:    src
Committed By:   joerg
Date:           Mon Apr  5 19:36:29 UTC 2010

Modified Files:
        src/share/man/man9: select.9

Log Message:
No trailing whitespace


To generate a diff of this commit:
cvs rdiff -u -r1.3 -r1.4 src/share/man/man9/select.9

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: src/share/man/man9/select.9
diff -u src/share/man/man9/select.9:1.3 src/share/man/man9/select.9:1.4
--- src/share/man/man9/select.9:1.3	Tue May 13 15:52:51 2008
+++ src/share/man/man9/select.9	Mon Apr  5 19:36:29 2010
@@ -1,4 +1,4 @@
-.\"     $NetBSD: select.9,v 1.3 2008/05/13 15:52:51 tnn Exp $
+.\"     $NetBSD: select.9,v 1.4 2010/04/05 19:36:29 joerg Exp $
 .\"
 .\" Copyright (C) 2002 Chad David <dav...@acns.ab.ca>. All rights reserved.
 .\"
@@ -79,11 +79,11 @@
 .Fn selrecord
 should only be called when the poll routine determines that the object
 is not ready for I/O: there are no events of interest pending.
-The check for pending I/O and call to 
+The check for pending I/O and call to
 .Fn selrecord
 must be atomic.
 Atomicity can be provided by holding the object's lock across the test
-and call to 
+and call to
 .Fn selrecord .
 For non-MPSAFE drivers, the global
 .Dv kernel_lock
@@ -92,9 +92,9 @@
 .Fn selnotify
 is called by the underlying object handling code in order to notify any waiting
 threads that an event of interest has occurred.
-The same lock held across the poll method and call to 
+The same lock held across the poll method and call to
 .Fn selrecord
-must be held across the call to 
+must be held across the call to
 .Fn selnotify .
 The lock prevents an event of interest being signalled while a thread is
 in the process of recording its interest.

Reply via email to