[PATCH 1/3] futex.2: tfix

[PATCH 1/3] futex.2: tfix

[Jakub Wilk]

---
 man2/futex.2 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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.
-- 
2.6.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 2/3] fcntl.2: tfix

[Jakub Wilk]

---
 man2/fcntl.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man2/fcntl.2 b/man2/fcntl.2
index 9abfb71..96c6993 100644
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -937,7 +937,7 @@ set etc.) to determine which file descriptors are available for I/O.
 
 Note that the file descriptor provided in
 .I si_fd
-is the one that that was specified during the
+is the one that was specified during the
 .BR F_SETSIG
 operation.
 This can lead to an unusual corner case.
-- 
2.6.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2/3] fcntl.2: tfix

[Michael Kerrisk (man-pages)]

On 12/30/2015 03:16 PM, Jakub Wilk wrote:
> ---
>  man2/fcntl.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)


Thanks, Jakub. Applied.

Cheers,

Michael


> diff --git a/man2/fcntl.2 b/man2/fcntl.2
> index 9abfb71..96c6993 100644
> --- a/man2/fcntl.2
> +++ b/man2/fcntl.2
> @@ -937,7 +937,7 @@ set etc.) to determine which file descriptors are available for I/O.
>  
>  Note that the file descriptor provided in
>  .I si_fd
> -is the one that that was specified during the
> +is the one that was specified during the
>  .BR F_SETSIG
>  operation.
>  This can lead to an unusual corner case.
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 3/3] Changes.old: tfix

[Jakub Wilk]

---
 Changes.old | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Changes.old b/Changes.old
index 80c82e6..7a7ce22 100644
--- a/Changes.old
+++ b/Changes.old
@@ -2117,7 +2117,7 @@ stat.2
 
 frexp.3
     Volker Reichelt / mtk
-        Fixed to point out that that frexp() returns a number whose
+        Fixed to point out that frexp() returns a number whose
         *absolute* value is >= 0.5 and < 1.  Amended the example
         program to demonstrate this.
 
-- 
2.6.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 3/3] Changes.old: tfix

[Michael Kerrisk (man-pages)]

On 12/30/2015 03:16 PM, Jakub Wilk wrote:
> ---
>  Changes.old | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, Jakub. Applied.

Cheers,

Michael


> diff --git a/Changes.old b/Changes.old
> index 80c82e6..7a7ce22 100644
> --- a/Changes.old
> +++ b/Changes.old
> @@ -2117,7 +2117,7 @@ stat.2
>  
>  frexp.3
>      Volker Reichelt / mtk
> -        Fixed to point out that that frexp() returns a number whose
> +        Fixed to point out that frexp() returns a number whose
>          *absolute* value is >= 0.5 and < 1.  Amended the example
>          program to demonstrate this.
>  
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 1/3] futex.2: tfix

[Michael Kerrisk (man-pages)]

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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html