Applied. Thanks. On 02/14/2014 06:18 AM, Peng Haitao wrote: > The function sem_post() is thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/sem_post.3 | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/man3/sem_post.3 b/man3/sem_post.3 > index f8251f0..48ec1c7 100644 > --- a/man3/sem_post.3 > +++ b/man3/sem_post.3 > @@ -23,7 +23,7 @@ > .\" the source, must acknowledge the copyright and authors of this work. > .\" %%%LICENSE_END > .\" > -.TH SEM_POST 3 2012-05-13 "Linux" "Linux Programmer's Manual" > +.TH SEM_POST 3 2014-02-14 "Linux" "Linux Programmer's Manual" > .SH NAME > sem_post \- unlock a semaphore > .SH SYNOPSIS > @@ -58,6 +58,11 @@ is not a valid semaphore. > .B EOVERFLOW > .\" Added in POSIX.1-2008 TC1 (Austin Interpretation 213) > The maximum allowable value for a semaphore would be exceeded. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR sem_post () > +function is thread-safe. > .SH CONFORMING TO > POSIX.1-2001. > .SH NOTES > -- 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
