[PATCH 01/13] defer/rcuintro: Clearly point the QSBR described section

[SeongJae Park <sj@kernel.org>]

From: SeongJae Park <sj38.park@gmail.com>

'Toy Implementation' section of 'defer/rcuintro' says QSBR is described
in the section, but it's actually explained in detail in its previous
section, 'Waiting for Readers'.  This commit updates the sentence to
point the sepcific section for a better reference.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 defer/rcuintro.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/defer/rcuintro.tex b/defer/rcuintro.tex
index 2f4e7ee3..7007058b 100644
--- a/defer/rcuintro.tex
+++ b/defer/rcuintro.tex
@@ -621,7 +621,8 @@ Referring back to
 note that \co{route_lock} is used to synchronize between concurrent updaters
 invoking \co{ins_route()} and \co{del_route()}.
 However, this lock is not acquired by readers invoking \co{access_route()}:
-Readers are instead protected by the QSBR techniques described in this section.
+Readers are instead protected by the QSBR techniques described in
+\cref{sec:defer:Waiting for Readers}.
 
 Note that \co{ins_route()} simply returns the old value of \co{gptr}, which
 \cref{fig:defer:Insertion With Concurrent Readers} assumed would
-- 
2.17.1