Hello Haitao. Applied. Thanks, Michael On 03/18/2014 02:14 AM, penght@xxxxxxxxxxxxxx wrote: > The functions mempcpy() and wmempcpy() are thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/mempcpy.3 | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/man3/mempcpy.3 b/man3/mempcpy.3 > index 084aacb..4f18308 100644 > --- a/man3/mempcpy.3 > +++ b/man3/mempcpy.3 > @@ -7,7 +7,7 @@ > .\" Heavily based on glibc infopages, copyright Free Software Foundation > .\" > .\" aeb, 2003, polished a little > -.TH MEMPCPY 3 2008-08-12 "GNU" "Linux Programmer's Manual" > +.TH MEMPCPY 3 2014-03-18 "GNU" "Linux Programmer's Manual" > .SH NAME > mempcpy, wmempcpy \- copy memory area > .SH SYNOPSIS > @@ -57,6 +57,13 @@ wide characters. > .SH VERSIONS > .BR mempcpy () > first appeared in glibc in version 2.1. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR mempcpy () > +and > +.BR wmempcpy () > +functions are thread-safe. > .SH CONFORMING TO > This function is a GNU extension. > .SH EXAMPLE > -- 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
