path: root/Documentation/RCU
diff options
authorTobias Klauser <>2020-07-02 18:28:10 +0200
committerPaul E. McKenney <>2020-08-24 14:29:16 -0700
commit77f808607a62c3685381a5732a88b30bad8893b5 (patch)
treebf26e3561ed55aa4c04c26dc457d63eb67329268 /Documentation/RCU
parent9123e3a74ec7b934a4a099e98af6a61c2f80bbf5 (diff)
docs: Fix typo in synchronize_rcu() function name
s/sychronize_rcu/synchronize_rcu/ Signed-off-by: Tobias Klauser <> Signed-off-by: Paul E. McKenney <>
Diffstat (limited to 'Documentation/RCU')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/RCU/whatisRCU.rst b/Documentation/RCU/whatisRCU.rst
index c7f147b8034f..fb3ff76c3e73 100644
--- a/Documentation/RCU/whatisRCU.rst
+++ b/Documentation/RCU/whatisRCU.rst
@@ -360,7 +360,7 @@ order to amortize their overhead over many uses of the corresponding APIs.
There are at least three flavors of RCU usage in the Linux kernel. The diagram
above shows the most common one. On the updater side, the rcu_assign_pointer(),
-sychronize_rcu() and call_rcu() primitives used are the same for all three
+synchronize_rcu() and call_rcu() primitives used are the same for all three
flavors. However for protection (on the reader side), the primitives used vary
depending on the flavor: