From: Ma Shimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cfree.3: ATTRIBUTES: Note function that is thread-safe
Date: Thu, 29 Jan 2015 09:31:17 +0800 [thread overview]
Message-ID: <54C98D65.9050100@cn.fujitsu.com> (raw)
In-Reply-To: <54C8C28F.2040107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hello Michael,
On 01/28/2015 07:05 PM, Michael Kerrisk (man-pages) wrote:
>> +.BR attributes (7).
>> > +.TS
>> > +allbox;
>> > +lb lb lb
>> > +l l l.
>> > +Interface Attribute Value
>> > +T{
>> > +.BR cfree ()
>> > +T} Thread safety MT-Safe /* In glibc */
> What is the "?* In glibc */" for?
This page records different versions of cfree.
Like cfree in SunOS 4, SCO OpenServer, glibc and so on.
I just can confirm thread safety of cfree in glibc.
So, I added a comment to help users understand which cfree
I'm declaring.
Did I miss something or any good ideas?
Best regards
--
Ma Shimiao
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
--
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
next prev parent reply other threads:[~2015-01-29 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 6:09 [PATCH] cfree.3: ATTRIBUTES: Note function that is thread-safe Ma Shimiao
[not found] ` <1422425343-20809-1-git-send-email-mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-01-28 11:05 ` Michael Kerrisk (man-pages)
[not found] ` <54C8C28F.2040107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-29 1:31 ` Ma Shimiao [this message]
[not found] ` <54C98D65.9050100-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-01-29 5:55 ` 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=54C98D65.9050100@cn.fujitsu.com \
--to=mashimiao.fnst-bthxqxjhjhxqfuhtdcdx3a@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 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.