From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org"
<penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
"carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org"
<carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org>,
"aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] random_r.3: ATTRIBUTES: Note functions that are thread-safe
Date: Tue, 01 Apr 2014 20:15:19 +0200 [thread overview]
Message-ID: <533B0237.2000207@gmail.com> (raw)
In-Reply-To: <1395735702-6364-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Thanks, Haitao! Applied.
Cheers,
Michael
On 03/25/2014 09:24 AM, penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org wrote:
> The functions random_r(), srandom_r(), initstate_r() and
> setstate_r() are thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/random_r.3 | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/man3/random_r.3 b/man3/random_r.3
> index 829eb81..92fe430 100644
> --- a/man3/random_r.3
> +++ b/man3/random_r.3
> @@ -23,7 +23,7 @@
> .\" %%%LICENSE_END
> .\"
> .\"
> -.TH RANDOM_R 3 2013-04-19 "GNU" "Linux Programmer's Manual"
> +.TH RANDOM_R 3 2014-03-25 "GNU" "Linux Programmer's Manual"
> .SH NAME
> random_r, srandom_r, initstate_r, setstate_r \- reentrant
> random number generator
> @@ -125,6 +125,15 @@ or
> argument to
> .BR random_r ()
> was NULL.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR random_r (),
> +.BR srandom_r (),
> +.BR initstate_r (),
> +and
> +.BR setstate_r ()
> +functions are thread-safe.
> .SH CONFORMING TO
> These functions are nonstandard glibc extensions.
> .\" These functions appear to be on Tru64, but don't seem to be on
>
--
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-04-01 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 8:24 [PATCH] random_r.3: ATTRIBUTES: Note functions that are thread-safe penght-BthXqXjhjHXQFUHtdCDX3A
[not found] ` <1395735702-6364-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-04-01 18:15 ` 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=533B0237.2000207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).