linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] wmemchr.3: Reformat thread-safety information
Date: Fri, 20 Jun 2014 07:53:21 +0200	[thread overview]
Message-ID: <53A3CC51.7030101@gmail.com> (raw)
In-Reply-To: <1403225013-17384-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thank you, Haitao. Applied.

Might I ask you to review my changes to the following:

    adjtime.3
    aio_error.3
    aio_return.3
    alloca.3
    asinh.3
    atan.3
    basename.3
    bcmp.3
    bcopy.3
    bsd_signal.3
    byteorder.3
    bzero.3
    catgets.3
    cbrt.3
    ceil.3
    cimag.3
    clock_getcpuclockid.3
    conj.3
    copysign.3
    cos.3
    cproj.3
    creal.3
    crypt.3
    daemon.3
    des_crypt.3
    difftime.3
    dirfd.3
    div.3
    drand48_r.3
    dysize.3
    ecvt.3
    encrypt.3
    erf.3
    erfc.3
    ether_aton.3

Mainly, I'd like you to double check that I do not introduce errors
(e.g., changing "not thread safe" to "MT-Safe"). There's a lot of 
tedious cut and paste work involved, so there's a chance to add
an error. (I already reviewed my changes, but I may have missed
something.)

Cheers,

Michael



On 06/20/2014 02:43 AM, Peng Haitao wrote:
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/wmemchr.3 | 13 ++++++++++---
>  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/man3/wmemchr.3 b/man3/wmemchr.3
> index e038f74..d4fe235 100644
> --- a/man3/wmemchr.3
> +++ b/man3/wmemchr.3
> @@ -49,10 +49,17 @@ or NULL if
>  does
>  not occur among these.
>  .SH ATTRIBUTES
> -.SS Multithreading (see pthreads(7))
> -The
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lb lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
>  .BR wmemchr ()
> -function is thread-safe.
> +T}	Thread safety	MT-Safe
> +.TE
>  .SH CONFORMING TO
>  C99.
>  .SH SEE ALSO
> 


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

  parent reply	other threads:[~2014-06-20  5:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  0:43 [PATCH] wmemchr.3: Reformat thread-safety information Peng Haitao
     [not found] ` <1403225013-17384-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-06-20  5:53   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <53A3CC51.7030101-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-25  1:36       ` Peng Haitao
     [not found]         ` <53AA278A.20607-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-06-25  9:02           ` Michael Kerrisk (man-pages)

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=53A3CC51.7030101@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    --cc=qianl.fnst-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).