linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Lei <qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: "mtk.manpages" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	carlos <carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org>,
	aoliva <aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] mq_getattr.3: ATTRIBUTES: Note functions that are thread-safe
Date: Mon, 9 Jun 2014 18:37:53 +0800	[thread overview]
Message-ID: <1402310273.1804.52.camel@fedora> (raw)
In-Reply-To: <1402307414.1804.42.camel@fedora>

The functions mq_getattr() and mq_setattr() are thread safe.

Signed-off-by: Qian Lei <qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/mq_getattr.3 | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/man3/mq_getattr.3 b/man3/mq_getattr.3
index 0fe370d..1c2321f 100644
--- a/man3/mq_getattr.3
+++ b/man3/mq_getattr.3
@@ -134,6 +134,13 @@ is invalid.
 .I newattr\->mq_flags
 contained set bits other than
 .BR O_NONBLOCK .
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_getattr ()
+and
+.BR mq_setattr ()
+functions are thread-safe.
 .SH CONFORMING TO
 POSIX.1-2001.
 .SH NOTES
-- 
1.8.3.1

--
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:[~2014-06-09 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  9:50 [PATCH] mq_getattr.3: ATTRIBUTES: Note function that is thread-safe Qian Lei
2014-06-09 10:37 ` Qian Lei [this message]
2014-06-10 14:46 ` 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=1402310273.1804.52.camel@fedora \
    --to=qianl.fnst-bthxqxjhjhxqfuhtdcdx3a@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=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).