From: 黄建忠 <jianzhong.huang@i-soft.com.cn>
To: musl <musl@lists.openwall.com>
Subject: the prototype decl of memcpy/memcmp/calloc/free should not in sched.h
Date: Fri, 31 Oct 2014 11:03:35 +0800 [thread overview]
Message-ID: <tencent_72C2AF5B277E00AE5BC0A201@qq.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
Hi, there,
sched.h in musl should not contains the prototype declarations of "memcpy/memcmp/calloc/free" func.
memcpy/memcmp already in string.h
calloc/free already in stdlib.h
Any reason they should exist in sched.h?
[-- Attachment #2: Type: text/html, Size: 319 bytes --]
next reply other threads:[~2014-10-31 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 3:03 黄建忠 [this message]
2014-10-31 3:24 ` Rich Felker
2014-10-31 3:42 ` the prototype decl of memcpy/memcmp/calloc/free shouldnot " 黄建忠
2014-11-01 16:22 ` Szabolcs Nagy
2014-11-01 17:02 ` Rich Felker
2014-11-01 20:49 ` Alexander Monakov
2014-11-02 4:48 ` Rich Felker
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=tencent_72C2AF5B277E00AE5BC0A201@qq.com \
--to=jianzhong.huang@i-soft.com.cn \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).