Note that \IXr{} works as expected in the main text.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
defer/rcuintro.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/defer/rcuintro.tex b/defer/rcuintro.tex
index dc464742..069ccfd7 100644
--- a/defer/rcuintro.tex
+++ b/defer/rcuintro.tex
@@ -202,7 +202,7 @@ pair can be enclosed within another.
In this case, the nested set of RCU read-side critical sections act as
one large critical section covering the full extent of the nested set.
The third read-side API member, \apik{rcu_dereference()}, fetches an
-RCU-protected pointer.
+\IXr{RCU-protected pointer}.
Conceptually, \co{rcu_dereference()} simply loads from memory, but we
will see in
\cref{sec:defer:Publish-Subscribe Mechanism}
@@ -213,7 +213,7 @@ that dereference this pointer.
\QuickQuiz{
What is an RCU-protected pointer?
}\QuickQuizAnswer{
- A pointer to RCU-protected data.
+ A pointer to \IXr{RCU-protected data}.
RCU-protected data is in turn a block of dynamically allocated
memory whose freeing will be deferred such that an RCU grace
period will elapse between the time that there were no longer
--
2.17.1
