On 07/03/13 03:27, Peng Haitao wrote: > The function clock_getcpuclockid() is thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> Thanks. Applied. >From now on (because I have now started incorporating your patches in mainline), please update the date in the .TH line in patches. Thanks, Michael > --- > man3/clock_getcpuclockid.3 | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/man3/clock_getcpuclockid.3 b/man3/clock_getcpuclockid.3 > index 42d0775..747dc76 100644 > --- a/man3/clock_getcpuclockid.3 > +++ b/man3/clock_getcpuclockid.3 > @@ -85,6 +85,11 @@ There is no process with the ID > The > .BR clock_getcpuclockid () > function is available in glibc since version 2.2. > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR clock_getcpuclockid () > +function is thread-safe. > .SH CONFORMING TO > POSIX.1-2001. > .SH NOTES > -- 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
