From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] kconfig: fix sparse warnings in nconfig
Date: Fri, 23 Jun 2017 12:21:48 +0900 [thread overview]
Message-ID: <CAK7LNASXArO+hBs780zjXXUw+HxrhkLqn-T6vNiQWd_z1LUihQ@mail.gmail.com> (raw)
In-Reply-To: <c3e8b332-3e13-3483-e893-c0aed498fbe9@infradead.org>
2017-05-23 10:44 GMT+09:00 Randy Dunlap <rdunlap@infradead.org>:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix sparse warnings in scripts/kconfig/nconf* ('make nconfig'):
>
> ../scripts/kconfig/nconf.c:1071:32: warning: Using plain integer as NULL pointer
> ../scripts/kconfig/nconf.c:1238:30: warning: Using plain integer as NULL pointer
> ../scripts/kconfig/nconf.c:511:51: warning: Using plain integer as NULL pointer
> ../scripts/kconfig/nconf.c:1460:6: warning: symbol 'setup_windows' was not declared. Should it be static?
> ../scripts/kconfig/nconf.c:274:12: warning: symbol 'current_instructions' was not declared. Should it be static?
> ../scripts/kconfig/nconf.c:308:22: warning: symbol 'function_keys' was not declared. Should it be static?
> ../scripts/kconfig/nconf.gui.c:132:17: warning: non-ANSI function declaration of function 'set_colors'
> ../scripts/kconfig/nconf.gui.c:195:24: warning: Using plain integer as NULL pointer
>
> nconf.gui.o before/after files are the same.
> nconf.o before/after files are the same until the 'static' function
> declarations are added.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied to linux-kbuild/fixes. Thanks!
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2017-06-23 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 1:44 [PATCH] kconfig: fix sparse warnings in nconfig Randy Dunlap
2017-06-23 3:21 ` Masahiro Yamada [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=CAK7LNASXArO+hBs780zjXXUw+HxrhkLqn-T6vNiQWd_z1LUihQ@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).