linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
	aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] qecvt.3: ATTRIBUTES: Note functions that are not thread-safe
Date: Sat, 18 May 2013 20:06:14 +0200	[thread overview]
Message-ID: <5197C316.9020503@gmail.com> (raw)
In-Reply-To: <1368585802-8689-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

On 05/15/13 04:43, Peng Haitao wrote:
> The functions qecvt() and qfcvt() are not thread safe.

Applied to my local branch for this work.

Thank you, Peng.

Cheers,

Michael

> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/qecvt.3 | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/man3/qecvt.3 b/man3/qecvt.3
> index 9cfa68d..07cbe59 100644
> --- a/man3/qecvt.3
> +++ b/man3/qecvt.3
> @@ -69,6 +69,17 @@ See
>  .BR ecvt (3)
>  and
>  .BR gcvt (3).
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The functions
> +.BR qecvt ()
> +and
> +.BR qfcvt ()
> +are not thread-safe.
> +.LP
> +The function
> +.BR qgcvt ()
> +is thread-safe.
>  .SH CONFORMING TO
>  SVr4.
>  Not seen in most common UNIX implementations,
> 

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

      parent reply	other threads:[~2013-05-18 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  2:43 [PATCH] qecvt.3: ATTRIBUTES: Note functions that are not thread-safe Peng Haitao
     [not found] ` <1368585802-8689-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-18 18:06   ` Michael Kerrisk [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=5197C316.9020503@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 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).