From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org"
<penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
"carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org"
<carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org>,
"aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] mempcpy.3: ATTRIBUTES: Note functions that are thread-safe
Date: Tue, 18 Mar 2014 03:47:46 +0100 [thread overview]
Message-ID: <5327B3D2.70709@gmail.com> (raw)
In-Reply-To: <1395105147-3817-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Hello Haitao.
Applied.
Thanks,
Michael
On 03/18/2014 02:14 AM, penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org wrote:
> The functions mempcpy() and wmempcpy() are thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/mempcpy.3 | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/man3/mempcpy.3 b/man3/mempcpy.3
> index 084aacb..4f18308 100644
> --- a/man3/mempcpy.3
> +++ b/man3/mempcpy.3
> @@ -7,7 +7,7 @@
> .\" Heavily based on glibc infopages, copyright Free Software Foundation
> .\"
> .\" aeb, 2003, polished a little
> -.TH MEMPCPY 3 2008-08-12 "GNU" "Linux Programmer's Manual"
> +.TH MEMPCPY 3 2014-03-18 "GNU" "Linux Programmer's Manual"
> .SH NAME
> mempcpy, wmempcpy \- copy memory area
> .SH SYNOPSIS
> @@ -57,6 +57,13 @@ wide characters.
> .SH VERSIONS
> .BR mempcpy ()
> first appeared in glibc in version 2.1.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR mempcpy ()
> +and
> +.BR wmempcpy ()
> +functions are thread-safe.
> .SH CONFORMING TO
> This function is a GNU extension.
> .SH EXAMPLE
>
--
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-03-18 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 1:14 [PATCH] mempcpy.3: ATTRIBUTES: Note functions that are thread-safe penght-BthXqXjhjHXQFUHtdCDX3A
[not found] ` <1395105147-3817-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-03-18 2:47 ` 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=5327B3D2.70709@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).