From: MaShimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] log.3:ATTRIBUTES: Note functions that are thread-safe
Date: Wed, 24 Dec 2014 16:55:15 +0800 [thread overview]
Message-ID: <549A7F73.9070800@cn.fujitsu.com> (raw)
In-Reply-To: <1418197854-20398-1-git-send-email-mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Ping.
On 12/10/2014 03:50 PM, Ma Shimiao wrote:
> The function log(), logf() and logl() are thread safe.
>
> Signed-off-by: Ma Shimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/log.3 | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/man3/log.3 b/man3/log.3
> index 96be9ef..e12c9b1 100644
> --- a/man3/log.3
> +++ b/man3/log.3
> @@ -125,6 +125,20 @@ is set to
> A divide-by-zero floating-point exception
> .RB ( FE_DIVBYZERO )
> is raised.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw24 lb lb
> +l l l.
> +Interface Attribute Value
> +T{
> +.BR log (),
> +.BR logf (),
> +.BR logl ()
> +T} Thread safety MT-Safe
> +.TE
> .SH CONFORMING TO
> C99, POSIX.1-2001.
> The variant returning
>
--
Ma Shimiao
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
--
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
next prev parent reply other threads:[~2014-12-24 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 7:50 [PATCH] log.3:ATTRIBUTES: Note functions that are thread-safe Ma Shimiao
[not found] ` <1418197854-20398-1-git-send-email-mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-12-24 8:55 ` MaShimiao [this message]
2014-12-30 13:23 ` Michael Kerrisk (man-pages)
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=549A7F73.9070800@cn.fujitsu.com \
--to=mashimiao.fnst-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).