From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] fread.3: ATTRIBUTES: Note functions that are thread-safe
Date: Tue, 29 Jul 2014 10:09:07 +0800 [thread overview]
Message-ID: <1406599747-26274-1-git-send-email-penght@cn.fujitsu.com> (raw)
The functions fread() and fwrite() are thread safe.
Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
man3/fread.3 | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/man3/fread.3 b/man3/fread.3
index ab81d4b..740e6ef 100644
--- a/man3/fread.3
+++ b/man3/fread.3
@@ -100,6 +100,19 @@ does not distinguish between end-of-file and error, and callers must use
and
.BR ferror (3)
to determine which occurred.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw17 lb lb
+l l l.
+Interface Attribute Value
+T{
+.BR fread (),
+.BR fwrite ()
+T} Thread safety MT-Safe
+.TE
.SH CONFORMING TO
C89, POSIX.1-2001.
.SH SEE ALSO
--
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
next reply other threads:[~2014-07-29 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 2:09 Peng Haitao [this message]
[not found] ` <1406599747-26274-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-07-29 4:48 ` [PATCH] fread.3: ATTRIBUTES: Note functions that are thread-safe 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=1406599747-26274-1-git-send-email-penght@cn.fujitsu.com \
--to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=qianl.fnst-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.