From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] pthread_equal.3: ATTRIBUTES: Note function that is thread-safe
Date: Fri, 23 May 2014 07:10:52 +0200 [thread overview]
Message-ID: <537ED85C.9050005@gmail.com> (raw)
In-Reply-To: <1400821306-373-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Thanks Haitao. Applied!
Cheers,
Michael
On 05/23/2014 07:01 AM, Peng Haitao wrote:
> The function pthread_equal() is thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/pthread_equal.3 | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/man3/pthread_equal.3 b/man3/pthread_equal.3
> index 23dfef1..0cd3495 100644
> --- a/man3/pthread_equal.3
> +++ b/man3/pthread_equal.3
> @@ -23,7 +23,7 @@
> .\" the source, must acknowledge the copyright and authors of this work.
> .\" %%%LICENSE_END
> .\"
> -.TH PTHREAD_EQUAL 3 2009-03-30 "Linux" "Linux Programmer's Manual"
> +.TH PTHREAD_EQUAL 3 2014-05-23 "Linux" "Linux Programmer's Manual"
> .SH NAME
> pthread_equal \- compare thread IDs
> .SH SYNOPSIS
> @@ -44,6 +44,11 @@ If the two thread IDs are equal,
> returns a nonzero value; otherwise, it returns 0.
> .SH ERRORS
> This function always succeeds.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR pthread_equal ()
> +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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-05-23 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 5:01 [PATCH] pthread_equal.3: ATTRIBUTES: Note function that is thread-safe Peng Haitao
[not found] ` <1400821306-373-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-05-23 5:10 ` Michael Kerrisk (man-pages) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=537ED85C.9050005@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.