On 22.10.2013 14:35, Peng Haitao wrote: > The function bcopy() is thread safe. Applied. Thanks, Michael > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/bcopy.3 | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/man3/bcopy.3 b/man3/bcopy.3 > index 2c79434..81891d3 100644 > --- a/man3/bcopy.3 > +++ b/man3/bcopy.3 > @@ -30,7 +30,7 @@ > .\" Modified Sun Feb 26 14:52:00 1995 by Rik Faith <faith@xxxxxxxxxx> > .\" Modified Tue Oct 22 23:48:10 1996 by Eric S. Raymond <esr@xxxxxxxxxxx> > .\" " > -.TH BCOPY 3 2009-03-15 "Linux" "Linux Programmer's Manual" > +.TH BCOPY 3 2013-10-22 "Linux" "Linux Programmer's Manual" > .SH NAME > bcopy \- copy byte sequence > .SH SYNOPSIS > @@ -51,6 +51,11 @@ to > The result is correct, even when both areas overlap. > .SH RETURN VALUE > None. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR bcopy () > +function is thread-safe. > .SH CONFORMING TO > 4.3BSD. > This function is deprecated (marked as LEGACY in POSIX.1-2001): use > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ My next Linux/UNIX system programming course: -- 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
