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] a64l.3: ATTRIBUTES: Note function that is not thread-safe
Date: Tue, 21 May 2013 13:11:13 +0200 [thread overview]
Message-ID: <519B5651.1000108@gmail.com> (raw)
In-Reply-To: <1369026746-9831-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 05/20/13 07:12, Peng Haitao wrote:
> The function l64a() is not thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Thanks, Peng. Applied in my local branch for this work.
Cheers,
Michael
> ---
> man3/a64l.3 | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/man3/a64l.3 b/man3/a64l.3
> index 1f14b68..762ec79 100644
> --- a/man3/a64l.3
> +++ b/man3/a64l.3
> @@ -59,6 +59,15 @@ a-z represent 38-63
> .fi
> .RE
> So 123 = 59*64^0 + 1*64^1 = "v/".
> +.SH ATTRIBUTES
> +.SS Multithreading(see pthreads(7))
> +The
> +.BR l64a ()
> +function is not thread-safe.
> +.LP
> +The
> +.BR a64l ()
> +function is thread-safe.
> .SH CONFORMING TO
> POSIX.1-2001.
> .SH NOTES
>
--
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:[~2013-05-21 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 5:12 [PATCH] a64l.3: ATTRIBUTES: Note function that is not thread-safe Peng Haitao
[not found] ` <1369026746-9831-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-21 11:11 ` 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=519B5651.1000108@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).