Drop the doubled word "up". Signed-off-by: Randy Dunlap <rdun...@infradead.org> Cc: Jonathan Corbet <cor...@lwn.net> Cc: linux-...@vger.kernel.org Cc: Peter Zijlstra <pet...@infradead.org> Cc: Ingo Molnar <mi...@redhat.com> Cc: Will Deacon <w...@kernel.org> --- Documentation/locking/ww-mutex-design.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200701.orig/Documentation/locking/ww-mutex-design.rst +++ linux-next-20200701/Documentation/locking/ww-mutex-design.rst @@ -49,7 +49,7 @@ However, the Wound-Wait algorithm is typ 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.
