Thanks, Haitao. Applied. Cheers, Michael On 03/17/2014 02:44 AM, penght@xxxxxxxxxxxxxx wrote: > The function memcpy() is thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/memcpy.3 | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/man3/memcpy.3 b/man3/memcpy.3 > index 7a0b890..9a19286 100644 > --- a/man3/memcpy.3 > +++ b/man3/memcpy.3 > @@ -27,7 +27,7 @@ > .\" Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991) > .\" 386BSD man pages > .\" Modified Sun Jul 25 10:41:09 1993 by Rik Faith (faith@xxxxxxxxxx) > -.TH MEMCPY 3 2010-11-15 "" "Linux Programmer's Manual" > +.TH MEMCPY 3 2014-03-17 "" "Linux Programmer's Manual" > .SH NAME > memcpy \- copy memory area > .SH SYNOPSIS > @@ -49,6 +49,11 @@ if the memory areas do overlap. > The > .BR memcpy () > function returns a pointer to \fIdest\fP. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR memcpy () > +function is thread-safe. > .SH CONFORMING TO > SVr4, 4.3BSD, C89, C99, POSIX.1-2001. > .SH SEE ALSO > -- 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
