All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ma Shimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Ma Shimiao
	<mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Subject: [PATCH] catan.3: ATTRIBUTES: Note functions that are thread-safe
Date: Wed, 4 Feb 2015 13:55:20 +0800	[thread overview]
Message-ID: <1423029320-11638-1-git-send-email-mashimiao.fnst@cn.fujitsu.com> (raw)

The functions catan(), catanf() and catanl() are thread safe.
Their markings match glibc markings.

Signed-off-by: Ma Shimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/catan.3 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/man3/catan.3 b/man3/catan.3
index 13e1023..ee4fbe9 100644
--- a/man3/catan.3
+++ b/man3/catan.3
@@ -33,6 +33,20 @@ One has:
 .fi
 .SH VERSIONS
 These functions first appeared in glibc in version 2.1.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw28 lb lb
+l l l.
+Interface  Attribute   Value
+T{
+.BR catan (),
+.BR catanf (),
+.BR catanl ()
+T} Thread safety   MT-Safe
+.TE
 .SH CONFORMING TO
 C99.
 .SH EXAMPLE
-- 
1.9.3

--
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

             reply	other threads:[~2015-02-04  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  5:55 Ma Shimiao [this message]
     [not found] ` <1423029320-11638-1-git-send-email-mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-02-04  6:14   ` [PATCH] catan.3: ATTRIBUTES: Note functions that are thread-safe Michael Kerrisk (man-pages)
     [not found]     ` <54D1B8AF.7070407-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-04  6:18       ` Ma Shimiao

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=1423029320-11638-1-git-send-email-mashimiao.fnst@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 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.