From: SeongJae Park <sj38.park@xxxxxxxxx>
Every \cref{} content is in a single line and it helps grep-like
scripting. However two \cref{}s are broken into two lines. Make those
single lines for consistency and easier grep.
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
datastruct/datastruct.tex | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/datastruct/datastruct.tex b/datastruct/datastruct.tex
index 9dffaf37..4c7f9fe2 100644
--- a/datastruct/datastruct.tex
+++ b/datastruct/datastruct.tex
@@ -1551,8 +1551,7 @@ and \clnref{acq_oldcur} acquires that bucket's spinlock.
\co{hashtab_del()} functions must be enclosed
in RCU read-side critical sections, courtesy of
\co{hashtab_lock_mod()} and \co{hashtab_unlock_mod()} in
- \cref{lst:datastruct:Resizable Hash-Table Update-Side Concurrency
- Control}.
+ \cref{lst:datastruct:Resizable Hash-Table Update-Side Concurrency Control}.
\end{fcvref}
}\QuickQuizEnd
@@ -1584,8 +1583,7 @@ the old hash table, and finally \clnref{ret_success} returns success.
\begin{fcvref}[ln:datastruct:hash_resize:lock_unlock_mod]
Together with the \co{READ_ONCE()}
on \clnref{l:ifresized} in \co{hashtab_lock_mod()}
- of \cref{lst:datastruct:Resizable Hash-Table Update-Side
- Concurrency Control},
+ of \cref{lst:datastruct:Resizable Hash-Table Update-Side Concurrency Control},
it tells the compiler that the non-initialization accesses
to \co{->ht_resize_cur} must remain because reads
from \co{->ht_resize_cur} really can race with writes,
--
2.17.1
