From 7b6e73f23104a50b898da1065cf9d3bf8b6a3bca Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Sat, 29 Jun 2019 17:26:04 -0700 Subject: more .adoc markup fixes. This is mostly mechanical-ish fixups to adjust markup style for cross references. A bit of care and feeding needed, so we haven't finished the list, but this gets a significant chunk of them. --- docs/man/nng_cv_wake1.3supp.adoc | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'docs/man/nng_cv_wake1.3supp.adoc') diff --git a/docs/man/nng_cv_wake1.3supp.adoc b/docs/man/nng_cv_wake1.3supp.adoc index cea7387c..2dd23129 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 `<>` or -`<>` functions. +to be signaled in the xref:nng_cv_wait.3supp.adoc[`nng_cv_wait()`] or +xref:nng_cv_until.3supp.adoc[`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 `<>`. +When in doubt, it is safer to use xref:nng_cv_wake.3supp.adoc[`nng_cv_wake()`]. == RETURN VALUES @@ -52,11 +52,11 @@ None. == SEE ALSO [.text-left] -<>, -<>, -<>, -<>, -<>, -<>, -<>, -<> +xref:nng_cv_alloc.3supp.adoc[nng_cv_alloc(3supp)], +xref:nng_cv_until.3supp.adoc[nng_cv_until(3supp)], +xref:nng_cv_wait.3supp.adoc[nng_cv_wait(3supp)], +xref:nng_cv_wake.3supp.adoc[nng_cv_wake(3supp)], +xref:nng_mtx_alloc.3supp.adoc[nng_mtx_alloc(3supp)], +xref:nng_mtx_lock.3supp.adoc[nng_mtx_lock(3supp)], +xref:nng_mtx_unlock.3supp.adoc[nng_mtx_unlock(3supp)], +xref:nng.7.adoc[nng(7)] -- cgit v1.2.3-70-g09d2