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] pthread_yield.3: ATTRIBUTES: Note function that is thread-safe
Date: Tue, 13 May 2014 10:31:18 +0200 [thread overview]
Message-ID: <5371D856.9070809@gmail.com> (raw)
In-Reply-To: <1399944717-19970-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Applied. Thanks, Haitao.
Cheers,
Michael
On 05/13/2014 03:31 AM, Peng Haitao wrote:
> The function pthread_yield() is thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/pthread_yield.3 | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/man3/pthread_yield.3 b/man3/pthread_yield.3
> index 894206b..ef8f171 100644
> --- a/man3/pthread_yield.3
> +++ b/man3/pthread_yield.3
> @@ -22,7 +22,7 @@
> .\" the source, must acknowledge the copyright and authors of this work.
> .\" %%%LICENSE_END
> .\"
> -.TH PTHREAD_YIELD 3 2013-03-05 "Linux" "Linux Programmer's Manual"
> +.TH PTHREAD_YIELD 3 2014-05-13 "Linux" "Linux Programmer's Manual"
> .SH NAME
> pthread_yield \- yield the processor
> .SH SYNOPSIS
> @@ -50,6 +50,11 @@ on error, it returns an error number.
> On Linux, this call always succeeds
> (but portable and future-proof applications should nevertheless
> handle a possible error return).
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR pthread_yield ()
> +function is thread-safe.
> .SH CONFORMING TO
> This call is nonstandard, but present on several other systems.
> Use the standardized
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2014-05-13 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 1:31 [PATCH] pthread_yield.3: ATTRIBUTES: Note function that is thread-safe Peng Haitao
[not found] ` <1399944717-19970-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-05-13 8:31 ` 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=5371D856.9070809@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 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.