summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2012-08-19 03:36:50 -0600
committerTom Tromey <tromey@redhat.com>2012-08-19 03:36:50 -0600
commit266c1c2fd96e4b25d755838dcf68c0c992a8a263 (patch)
treec0b812d927e70422f2c404ac872eb5a58a0926e6
parent1fb339bccd65db50adc2ad7f7290099808fc439d (diff)
downloademacs-266c1c2fd96e4b25d755838dcf68c0c992a8a263.tar.gz
minor docstring fixup
-rw-r--r--src/thread.c8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/thread.c b/src/thread.c
index 4c21418d1c3..608c3b8d8f1 100644
--- a/src/thread.c
+++ b/src/thread.c
@@ -348,9 +348,9 @@ CONDITION is the condition variable to wait on.
The mutex associated with CONDITION must be held when this is called.
It is an error if it is not held.
-This atomically releases the mutex and waits for CONDITION to be
-notified. When `condition-wait' returns, the mutex will again be
-locked by this thread. */)
+This releases the mutex and waits for CONDITION to be notified. When
+`condition-wait' returns, the mutex will again be locked by this
+thread. */)
(Lisp_Object condition)
{
struct Lisp_CondVar *cvar;
@@ -402,7 +402,7 @@ If ALL is non-nil, all waiting threads are awoken.
The mutex associated with CONDITION must be held when this is called.
It is an error if it is not held.
-This atomically releases the mutex when notifying CONDITION. When
+This releases the mutex when notifying CONDITION. When
`condition-notify' returns, the mutex will again be locked by this
thread. */)
(Lisp_Object condition, Lisp_Object all)