From: "Michael Kerrisk (man-pages)" <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] bcopy.3: ATTRIBUTES: Note function that is thread-safe
Date: Sat, 26 Oct 2013 11:26:19 +1300 [thread overview]
Message-ID: <526AF00B.1070404@gmail.com> (raw)
In-Reply-To: <1382405716-5116-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 22.10.2013 14:35, Peng Haitao wrote:
> The function bcopy() is thread safe.
Applied.
Thanks,
Michael
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/bcopy.3 | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/man3/bcopy.3 b/man3/bcopy.3
> index 2c79434..81891d3 100644
> --- a/man3/bcopy.3
> +++ b/man3/bcopy.3
> @@ -30,7 +30,7 @@
> .\" Modified Sun Feb 26 14:52:00 1995 by Rik Faith <faith-+5Oa3zvhR2o3uPMLIKxrzw@public.gmane.org>
> .\" Modified Tue Oct 22 23:48:10 1996 by Eric S. Raymond <esr-4uCgticg2UFBDgjK7y7TUQ@public.gmane.org>
> .\" "
> -.TH BCOPY 3 2009-03-15 "Linux" "Linux Programmer's Manual"
> +.TH BCOPY 3 2013-10-22 "Linux" "Linux Programmer's Manual"
> .SH NAME
> bcopy \- copy byte sequence
> .SH SYNOPSIS
> @@ -51,6 +51,11 @@ to
> The result is correct, even when both areas overlap.
> .SH RETURN VALUE
> None.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR bcopy ()
> +function is thread-safe.
> .SH CONFORMING TO
> 4.3BSD.
> This function is deprecated (marked as LEGACY in POSIX.1-2001): use
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
My next Linux/UNIX system programming course:
--
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-10-25 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 1:35 [PATCH] bcopy.3: ATTRIBUTES: Note function that is thread-safe Peng Haitao
[not found] ` <1382405716-5116-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-10-25 22:26 ` 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=526AF00B.1070404@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.