path: root/Documentation/locking
diff options
authorRandy Dunlap <>2020-07-03 14:36:49 -0700
committerJonathan Corbet <>2020-07-13 09:48:31 -0600
commit8b1a17c7c5c528f9f512ad2b1098feedcee289da (patch)
treedcf804ce1222ab09695b9d7cbd1300d90f6d406d /Documentation/locking
parent7d64394b5187e225b4e578d281a36e07495738ce (diff)
Documentation: locking: ww-mutex-design: drop duplicated word
Drop the doubled word "up". Signed-off-by: Randy Dunlap <> Cc: Jonathan Corbet <> Cc: Cc: Peter Zijlstra <> Cc: Ingo Molnar <> Cc: Will Deacon <> Link: Signed-off-by: Jonathan Corbet <>
Diffstat (limited to 'Documentation/locking')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/locking/ww-mutex-design.rst b/Documentation/locking/ww-mutex-design.rst
index 1846c199da23..54d9c17bb66b 100644
--- a/Documentation/locking/ww-mutex-design.rst
+++ b/Documentation/locking/ww-mutex-design.rst
@@ -49,7 +49,7 @@ However, the Wound-Wait algorithm is typically stated to generate fewer backoffs
compared to Wait-Die, but is, on the other hand, associated with more work than
Wait-Die when recovering from a backoff. Wound-Wait is also a preemptive
algorithm in that transactions are wounded by other transactions, and that
-requires a reliable way to pick up up the wounded condition and preempt the
+requires a reliable way to pick up the wounded condition and preempt the
running transaction. Note that this is not the same as process preemption. A
Wound-Wait transaction is considered preempted when it dies (returning
-EDEADLK) following a wound.