[PATCH] locking: Consistently append parentheses to pthread_cond_wait()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Some of 'pthread_cond_wait()' mentions have '()' suffix, which indicates
it's a function, but some mentions don't.  This commit adds the suffix
to all mentions to be consistent.

Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
 locking/locking.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/locking/locking.tex b/locking/locking.tex
index 14690b19..4ad5e4c4 100644
--- a/locking/locking.tex
+++ b/locking/locking.tex
@@ -528,8 +528,8 @@ prevents hangs due to lost wakeups.
 
 	Consider a program that acquires \co{mutex_a}, and then
 	\co{mutex_b}, in that order, and then passes \co{mutex_a}
-	to \co{pthread_cond_wait}.
-	Now, \co{pthread_cond_wait} will release \co{mutex_a}, but
+	to \co{pthread_cond_wait()}.
+	Now, \co{pthread_cond_wait()} will release \co{mutex_a}, but
 	will re-acquire it before returning.
 	If some other thread acquires \co{mutex_a} in the meantime
 	and then blocks on \co{mutex_b}, the program will deadlock.
-- 
2.17.1




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux