On 12/30/2015 03:16 PM, Jakub Wilk wrote: > --- > man2/futex.2 | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) Thanks, Jakub. Applied. Cheers, Michael > diff --git a/man2/futex.2 b/man2/futex.2 > index 7144bf1..8c6c023 100644 > --- a/man2/futex.2 > +++ b/man2/futex.2 > @@ -88,7 +88,7 @@ on the same futex word. > .\" Totally ordered with respect futex operations refers to semantics > .\" of the ACQUIRE/RELEASE operations and how they impact ordering of > .\" memory reads and writes. The kernel futex operations are protected > -.\" by spinlocks, which ensure that that all operations are serialized > +.\" by spinlocks, which ensure that all operations are serialized > .\" with respect to one another. > .\" > .\" This is a lot to attempt to define in this document. Perhaps a > @@ -125,11 +125,11 @@ wait operation. > This > .BR futex () > operation will block if and only if the lock is still acquired > -(i.e., the value in the futex word still matches the "acquiired state"). > +(i.e., the value in the futex word still matches the "acquired state"). > When releasing the lock, a thread has to first reset the > lock state to not acquired and then execute a futex > operation that wakes threads blocked on the lock flag used as a futex word > -(this can be be further optimized to avoid unnecessary wake-ups). > +(this can be further optimized to avoid unnecessary wake-ups). > See > .BR futex (7) > for more detail on how to use futexes. > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
