aboutsummaryrefslogtreecommitdiffstats
path: root/man3
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2018-11-17 07:41:18 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2018-11-17 07:41:18 +0100
commitda3ed81b4239ef140d7feee117841cc1099867c6 (patch)
treef656897e896f5b973bbc1967b603977d12ca33b5 /man3
parent0d255e74c098dd2ad420367503398ad7f8f82024 (diff)
downloadman-pages-da3ed81b4239ef140d7feee117841cc1099867c6.tar.gz
pthread_rwlockattr_setkind_np.3: tfix
Reported-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man3')
-rw-r--r--man3/pthread_rwlockattr_setkind_np.32
1 files changed, 1 insertions, 1 deletions
diff --git a/man3/pthread_rwlockattr_setkind_np.3 b/man3/pthread_rwlockattr_setkind_np.3
index 6b2b8db397..892b461f4d 100644
--- a/man3/pthread_rwlockattr_setkind_np.3
+++ b/man3/pthread_rwlockattr_setkind_np.3
@@ -94,7 +94,7 @@ read locks thus avoiding deadlocks.
.\" the pthread_rwlock_unlock() function n times).
.\"
.\" By making write-priority work correctly, I broke the above requirement,
-.\" because. I had no clue that recursive read locks are permissible.
+.\" because I had no clue that recursive read locks are permissible.
.\"
.\" If a thread which holds a read lock tries to acquire another read lock,
.\" and now one or more writers is waiting for a write lock, then the algorithm