linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: patchset for fgetgrent fgetpwent getspnam mallinfo sigpause and termios
Date: Fri, 11 Sep 2015 12:10:57 +0200	[thread overview]
Message-ID: <55F2A8B1.9070808@gmail.com> (raw)
In-Reply-To: <1441776711.22425.6.camel@G08FNSTD140232>

On 09/09/2015 07:31 AM, Zeng Linggang wrote:
> Hello,
> 
> Could someone help to review these?
> I think these codes is not really too much if you have scanned them.
> Please keep a little patience. :)

My apologies for the delay, Zeng Linggang. I'm a little too busy
at the moment.

Cheers,

Michael


> Thanks and best regards,
> Zeng
> 
> On Tue, 2015-09-01 at 16:00 +0800, Zeng Linggang wrote:
>> Hello,
>>
>> Ping! :)
>>
>> Thanks and best regards,
>> Zeng
>>
>> On Mon, 2015-08-24 at 18:19 +0800, Zeng Linggang wrote:
>>> Hello,
>>>
>>> This patchset is for fgetgrent.3, fgetpwent.3, sigpause.3, termios.3,
>>> getspnam.3 and mallinfo.3
>>>
>>> 1. fgetgrent.3 and fgetpwent.3:
>>>    We have some discussions about these two functions, the Subject:
>>>    "Re: question about markings of fgetgrent and fgetpwent"
>>>    However, something about the copyright impeded the progress.
>>>    I am sorry for that, if you are OK, please see these two patches below,
>>>    I have added some "FIXME:" descriptions in them.
>>>
>>> 2. getspnam.3
>>>    getspnam.3 is a little like fgetgrent.3 and fgetpwent.3, but there are not
>>>    markings in glibc document. I use the function names for the identifiers like
>>>    fgetgrent.3 and fgetpwent.3.
>>>
>>> 3. mallinfo.3
>>>    Hope the descriptions about "const:mallopt" could explain clearly enough in
>>>    the patch.
>>>
>>> 4. sigpause.3 and termios.3
>>>    These two functions are safety in Linux kernel, the markings in glibc manual
>>>    are more detailed. I also have added some "FIXME:" descriptions in them.
>>>
>>>
>>> Thanks and best regards,
>>> Zeng
>>> --
>>> 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
> 
> 
> 


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

  reply	other threads:[~2015-09-11 10:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 10:19 patchset for fgetgrent fgetpwent getspnam mallinfo sigpause and termios Zeng Linggang
     [not found] ` <1440411596-2566-1-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-08-24 10:19   ` [PATCH] fgetgrent.3: ATTRIBUTES: Note function that is not thread-safe Zeng Linggang
     [not found]     ` <1440411596-2566-2-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-09-11 10:06       ` Michael Kerrisk (man-pages)
2015-08-24 10:19   ` [PATCH] fgetpwent.3: " Zeng Linggang
     [not found]     ` <1440411596-2566-3-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-09-11 10:06       ` Michael Kerrisk (man-pages)
2015-08-24 10:19   ` [PATCH] getspnam.3: ATTRIBUTES: Note functions that are/aren't thread-safe Zeng Linggang
     [not found]     ` <1440411596-2566-4-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-09-11 10:06       ` Michael Kerrisk (man-pages)
2015-08-24 10:19   ` [PATCH] mallinfo.3: ATTRIBUTES: Note function that is not thread-safe Zeng Linggang
     [not found]     ` <1440411596-2566-5-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-09-11 10:06       ` Michael Kerrisk (man-pages)
2015-08-24 10:19   ` [PATCH] sigpause.3: srcfix: add FIXME Zeng Linggang
     [not found]     ` <1440411596-2566-6-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-09-11 10:07       ` Michael Kerrisk (man-pages)
2015-08-24 10:19   ` [PATCH] termios.3: " Zeng Linggang
     [not found]     ` <1440411596-2566-7-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-09-11 10:07       ` Michael Kerrisk (man-pages)
2015-09-01  8:00   ` patchset for fgetgrent fgetpwent getspnam mallinfo sigpause and termios Zeng Linggang
2015-09-09  5:31     ` Zeng Linggang
2015-09-11 10:10       ` Michael Kerrisk (man-pages) [this message]
     [not found]         ` <55F2A8B1.9070808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-12  7:00           ` Zeng Linggang

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=55F2A8B1.9070808@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=zenglg.jy-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).