diff options
Diffstat (limited to 'docs/man/nng_cv_wake1.3supp.adoc')
| -rw-r--r-- | docs/man/nng_cv_wake1.3supp.adoc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/man/nng_cv_wake1.3supp.adoc b/docs/man/nng_cv_wake1.3supp.adoc index 1938a702..29a4ed88 100644 --- a/docs/man/nng_cv_wake1.3supp.adoc +++ b/docs/man/nng_cv_wake1.3supp.adoc @@ -27,8 +27,8 @@ void nng_cv_wake1(nng_cv *cv); The `nng_cv_wake1()` wakes at most one thread waiting for the condition variable _cv_ -to be signaled in the <<nng_cv_wait.3supp#,`nng_cv_wait()`>> or -<<nng_cv_until.3supp#,`nng_cv_until()`>> functions. +to be signaled in the `<<nng_cv_wait.3supp#,nng_cv_wait()>>` or +`<<nng_cv_until.3supp#,nng_cv_until()>>` functions. The caller must have have ownership of the mutex that was used when _cv_ was allocated. @@ -39,7 +39,7 @@ will check, while holding the mutex. TIP: While this function avoids the "`thundering herd`" problem, the caller cannot predict which waiter will be woken, and so the design must ensure that it is sufficient that _any_ waiter be woken. -When in doubt, it is safer to use <<nng_cv_wake.3supp#,`nng_cv_wake()`>>. +When in doubt, it is safer to use `<<nng_cv_wake.3supp#,nng_cv_wake()>>`. == RETURN VALUES |