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] rint.3: ATTRIBUTES: Note functions that are thread-safe
Date: Mon, 02 Sep 2013 07:38:35 +0200 [thread overview]
Message-ID: <5224245B.3040402@gmail.com> (raw)
In-Reply-To: <1377508016-14246-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 08/26/13 11:06, Peng Haitao wrote:
> The functions nearbyint(), nearbyintf(), nearbyintl(), rint(),
> rintf() and rintl() are thread safe.
Applied. Thanks.
Cheers,
Michael
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/rint.3 | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/man3/rint.3 b/man3/rint.3
> index 8dde6bc..8bb9ba8 100644
> --- a/man3/rint.3
> +++ b/man3/rint.3
> @@ -24,7 +24,7 @@
> .\" the source, must acknowledge the copyright and authors of this work.
> .\" %%%LICENSE_END
> .\"
> -.TH RINT 3 2010-09-20 "" "Linux Programmer's Manual"
> +.TH RINT 3 2013-08-26 "" "Linux Programmer's Manual"
> .SH NAME
> nearbyint, nearbyintf, nearbyintl, rint, rintf, rintl \- round
> to nearest integer
> @@ -113,6 +113,17 @@ itself is returned.
> .SH ERRORS
> No errors occur.
> POSIX.1-2001 documents a range error for overflows, but see NOTES.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR nearbyint (),
> +.BR nearbyintf (),
> +.BR nearbyintl (),
> +.BR rint (),
> +.BR rintf (),
> +and
> +.BR rintl ()
> +functions are thread-safe.
> .SH CONFORMING TO
> C99, POSIX.1-2001.
> .SH NOTES
>
--
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:[~2013-09-02 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 9:06 [PATCH] rint.3: ATTRIBUTES: Note functions that are thread-safe Peng Haitao
[not found] ` <1377508016-14246-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-09-02 5:38 ` 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=5224245B.3040402@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).