[PATCH -perfbook 5/6] defer/rcufundamental: Fix typo ("cannot not return")

Akira Yokosawa <[email protected]> Tue, 23 Jun 2026 19:30:08 +0900
Newsgroups org.kernel.vger.perfbook
Message-ID <[email protected]>
Signed-off-by: Akira Yokosawa <[email protected]>
---
 defer/rcufundamental.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
index edb90e0d..7e06a5ab 100644
--- a/defer/rcufundamental.tex
+++ b/defer/rcufundamental.tex
@@ -220,7 +220,7 @@ pre-existing RCU read-side critical section to complete, and
 waiting for a \emph{grace
 period}~\cite{MathieuDesnoyers2012URCU,McKenney:2013:SDS:2483852.2483867}.
 
-In other words, \co{synchronize_rcu()} cannot not return until all
+In other words, \co{synchronize_rcu()} cannot return until all
 pre-existing RCU read-side critical sections have completed.
 In other words, if one task\footnote{
 	Or CPU, process, thread, or whatever name you prefer.}
@@ -281,7 +281,7 @@ thus guaranteeing that \co{r2}'s final value will be zero.
 But suppose that the \co{rcu_read_unlock()} ending a given task's RCU
 read-side critical section is executed after the return from a second
 task's call to \co{synchronize_rcu()}.
-Because \co{synchronize_rcu()} cannot not return until all task have
+Because \co{synchronize_rcu()} cannot return until all task have
 exited any pre-existing RCU read-side critical sections, it must be the
 case that the second task called \co{synchronize_rcu()} before first
 task executed the matching \co{rcu_read_lock()}.
-- 
2.43.0