linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org
Subject: Re: [PATCH v2] bindresvport.3: ATTRIBUTES: Note function that is thread-safe
Date: Mon, 20 May 2013 10:36:23 +0800	[thread overview]
Message-ID: <51998C27.7020308@cn.fujitsu.com> (raw)
In-Reply-To: <5197C76C.6070202-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


On 05/19/2013 02:24 AM, Michael Kerrisk wrote:
>> diff --git a/man3/bindresvport.3 b/man3/bindresvport.3
>> index d2e73a4..2c7152d 100644
>> --- a/man3/bindresvport.3
>> +++ b/man3/bindresvport.3
>> @@ -89,6 +89,16 @@ is not NULL and
>>  .I sin->sin_family
>>  is not
>>  .BR AF_INET .
>> +.SH ATTRIBUTES
>> +.SS Multithreading (see pthreads(7))
>> +Before glibc 2.17, the
>> +.BR bindresvport ()
>> +uses a static variable that is not protected, so it is not thread-safe.
> 
> Missing word "function" here (function uses..."). This was also the
> case in a number of the other patches you sent recently. (I fixed them all.)
> 

Thanks.

>> +Since glibc 2.17, the
>> +.BR bindresvport ()
> 
> (Missing word "function".)
>> +uses a lock to protect static variable, so it is thread-safe.
> 
> "uses a lock to protect *a* static variable"
> (I fixed this, and also in a few other patches.)
> 

Thanks.

>> +.\" Modified in commit f6da27e53695ad1cc0e2a9490358decbbfdff5e5
> 
> Here, its is enough just to write
> 
> +.\" commit f6da27e53695ad1cc0e2a9490358decbbfdff5e5
> 
> And I'd rearrange things a little, so that the patch is better as:
> 
> ==
> +Since glibc 2.17,
> +.\" commit f6da27e53695ad1cc0e2a9490358decbbfdff5e5
> +the
> +.BR bindresvport ()
> ...
> ==
> 
> I made that fix (and also in one other patch.)
> 

Thanks.

-- 
Best Regards,
Peng

> Cheers,
> 
> Michael
> 
> 
>>  .SH CONFORMING TO
>>  Not in POSIX.1-2001.
>>  Present on the BSDs, Solaris, and many other systems.
> 
> Thank you, Peng.
> 
> Cheers,
> 
> Michael
> 
> 
> --
> 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
> 

--
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:[~2013-05-20  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  6:46 [PATCH v2] bindresvport.3: ATTRIBUTES: Note function that is thread-safe Peng Haitao
     [not found] ` <1366785972-12231-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-18 18:24   ` Michael Kerrisk
     [not found]     ` <5197C76C.6070202-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-20  2:36       ` Peng Haitao [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=51998C27.7020308@cn.fujitsu.com \
    --to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).