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] mbrlen.3: ATTRIBUTES: Note function that is thread safe with exceptions
Date: Thu, 30 May 2013 13:06:01 +0200 [thread overview]
Message-ID: <51A73299.7020709@gmail.com> (raw)
In-Reply-To: <1369820111-7081-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 05/29/13 11:35, Peng Haitao wrote:
> The function mbrlen() is thread safe with exceptions.
Hi Peng,
Applied to my local branch. See comment below.
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/mbrlen.3 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man3/mbrlen.3 b/man3/mbrlen.3
> index da50230..882ffdb 100644
> --- a/man3/mbrlen.3
> +++ b/man3/mbrlen.3
> @@ -66,6 +66,12 @@ and sets \fIerrno\fP to \fBEILSEQ\fP, if an invalid multibyte sequence was
> encountered.
> It returns \fI(size_t)\ \-2\fP if it couldn't parse a complete multibyte
> character, meaning that \fIn\fP should be increased.
> +.SH ATTRIBUTES
> +.SS Multithreading(see pthreads(7))
Space added before "(see)" (and also in a number of other patches
you already sent.
Thanks,
Michael
> +The
> +.BR mbrlen ()
> +function is thread-safe with exceptions.
> +It is not thread-safe if called with a NULL \fIps\fP parameter.
> .SH CONFORMING TO
> C99.
> .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
next prev parent reply other threads:[~2013-05-30 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 9:35 [PATCH] mbrlen.3: ATTRIBUTES: Note function that is thread safe with exceptions Peng Haitao
[not found] ` <1369820111-7081-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-30 11:06 ` Michael Kerrisk [this message]
[not found] ` <51A73299.7020709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-04 8:15 ` Peng Haitao
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=51A73299.7020709@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.