From: Chen Zhou <chenzhou10@huawei.com>
To: <akpm@linux-foundation.org>, <sfr@canb.auug.org.au>,
<rppt@linux.ibm.com>, <keescook@chromium.org>
Cc: <linux-kernel@vger.kernel.org>, <chenzhou10@huawei.com>
Subject: [PATCH next] init/main.c: make some symbols static
Date: Wed, 15 Jan 2020 21:54:58 +0800 [thread overview]
Message-ID: <20200115135458.71460-1-chenzhou10@huawei.com> (raw)
Make variable xbc_namebuf and function boot_config_checksum static to
fix build warnings, warnings are as follows:
init/main.c:254:6:
warning: symbol 'xbc_namebuf' was not declared. Should it be static?
init/main.c:330:5:
warning: symbol 'boot_config_checksum' was not declared. Should it be static?
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
---
init/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/init/main.c b/init/main.c
index a77114f..3a95591 100644
--- a/init/main.c
+++ b/init/main.c
@@ -251,7 +251,7 @@ early_param("loglevel", loglevel);
#ifdef CONFIG_BOOT_CONFIG
-char xbc_namebuf[XBC_KEYLEN_MAX] __initdata;
+static char xbc_namebuf[XBC_KEYLEN_MAX] __initdata;
#define rest(dst, end) ((end) > (dst) ? (end) - (dst) : 0)
@@ -327,7 +327,7 @@ static char * __init xbc_make_cmdline(const char *key)
return new_cmdline;
}
-u32 boot_config_checksum(unsigned char *p, u32 size)
+static u32 boot_config_checksum(unsigned char *p, u32 size)
{
u32 ret = 0;
--
2.7.4
next reply other threads:[~2020-01-15 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 13:54 Chen Zhou [this message]
2020-01-15 14:20 ` [PATCH next] init/main.c: make some symbols static Mike Rapoport
2020-01-15 22:20 ` Masami Hiramatsu
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=20200115135458.71460-1-chenzhou10@huawei.com \
--to=chenzhou10@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
/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