From: SeongJae Park <sj38.park@xxxxxxxxx>
\co{} is used for some boolean return value and not for some other case.
To make it consistent, use \co{} for all.
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
defer/rcuapi.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/defer/rcuapi.tex b/defer/rcuapi.tex
index 425c64ff..9ac2d26c 100644
--- a/defer/rcuapi.tex
+++ b/defer/rcuapi.tex
@@ -785,7 +785,7 @@ Should a reader encounter a \co{NULL} pointer not matching the index of
the bucket it started from, that reader knows that an element it was
traversing was moved to some other bucket during the traversal, taking
that reader with it.
-The reader can use the \apik{is_a_nulls()} function (which returns true
+The reader can use the \apik{is_a_nulls()} function (which returns \co{true}
if passed an \co{hlist_nulls} \co{NULL} pointer) to determine when
it reaches the end of a list, and the \apik{get_nulls_value()} function
(which returns its argument's \co{NULL}-pointer identifier) to fetch
@@ -1156,7 +1156,7 @@ type of RCU read-side critical section.
Because \co{rcu_read_lock()} cannot be used from the idle loop,
and because energy-efficiency concerns have caused the idle loop
-to become quite ornate, \apik{rcu_is_watching()} returns true if
+to become quite ornate, \apik{rcu_is_watching()} returns \co{true} if
invoked in a context where use of \co{rcu_read_lock()} is legal.
Note again that \co{srcu_read_lock()} may be used from idle and
even offline CPUs, which means that \co{rcu_is_watching()} does not
--
2.17.1
