From: DU HUANPENG <no_rep1y@hotmail.com>
To: "t-kernel@googlegroups.com" <t-kernel@googlegroups.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Cc: "norep1y@21cn.com" <norep1y@21cn.com>, Du Huanpeng <u74147@gmail.com>
Subject: [PATCH] NULL: keep NULL definition in stddef.h only
Date: Wed, 13 Apr 2016 16:04:01 +0000 [thread overview]
Message-ID: <HK2PR04MB16188596FE161189D917398EBE960@HK2PR04MB1618.apcprd04.prod.outlook.com> (raw)
From: Du Huanpeng <u74147@gmail.com>
remove other local definition of NULL, use
#include <linux/stddef.h>
instead.
I use this command to search NULL definition,
grep -R "define\s*\<NULL\>"
hope there are no more definition of NULL.
from ISO/IEC 9899:TC3:
The macros are
NULL
which expands to an implementation-defined null pointer constant;
Signed-off-by: Du Huanpeng <u74147@gmail.com>
---
include/command.h | 5 +----
lib/bzlib_private.h | 11 +----------
2 files changed, 2 insertions(+), 14 deletions(-)
diff --git a/include/command.h b/include/command.h
index 3aca1a9..b938431 100644
--- a/include/command.h
+++ b/include/command.h
@@ -25,10 +25,7 @@
#include <linux/list.h>
#include <linux/stringify.h>
-
-#ifndef NULL
-#define NULL 0
-#endif
+#include <linux/stddef.h>
#ifndef __ASSEMBLY__
diff --git a/lib/bzlib_private.h b/lib/bzlib_private.h
index 87d8f94..de10dd4 100644
--- a/lib/bzlib_private.h
+++ b/lib/bzlib_private.h
@@ -67,6 +67,7 @@
#define _BZLIB_PRIVATE_H
#include <malloc.h>
+#include <linux/stddef.h>
#include "bzlib.h"
@@ -515,16 +516,6 @@ BZ2_hbCreateDecodeTables ( Int32*, Int32*, Int32*, UChar*,
#endif
-
-/*-- BZ_NO_STDIO seems to make NULL disappear on some platforms. --*/
-
-#ifdef BZ_NO_STDIO
-#ifndef NULL
-#define NULL 0
-#endif
-#endif
-
-
/*-------------------------------------------------------------*/
/*--- end bzlib_private.h ---*/
/*-------------------------------------------------------------*/
--
1.9.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2016-04-13 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 16:04 DU HUANPENG [this message]
2016-04-14 6:02 ` Sascha Hauer
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=HK2PR04MB16188596FE161189D917398EBE960@HK2PR04MB1618.apcprd04.prod.outlook.com \
--to=no_rep1y@hotmail.com \
--cc=barebox@lists.infradead.org \
--cc=norep1y@21cn.com \
--cc=t-kernel@googlegroups.com \
--cc=u74147@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox