mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: DU HUANPENG <no_rep1y@hotmail.com>, g@pengutronix.de
Cc: Du Huanpeng <u74147@gmail.com>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>,
	"norep1y@21cn.com" <norep1y@21cn.com>,
	"t-kernel@googlegroups.com" <t-kernel@googlegroups.com>
Subject: Re: [PATCH] NULL: keep NULL definition in stddef.h only
Date: Thu, 14 Apr 2016 08:02:22 +0200	[thread overview]
Message-ID: <20160414060222.GX9102@pengutronix.de> (raw)
In-Reply-To: <HK2PR04MB16188596FE161189D917398EBE960@HK2PR04MB1618.apcprd04.prod.outlook.com>

On Wed, Apr 13, 2016 at 04:04:01PM +0000, DU HUANPENG wrote:
> 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(-)

Applied, thanks

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2016-04-14  6:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 16:04 DU HUANPENG
2016-04-14  6:02 ` Sascha Hauer [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=20160414060222.GX9102@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=g@pengutronix.de \
    --cc=no_rep1y@hotmail.com \
    --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