From: Tom Lendacky <thomas.lendacky@amd.com>
To: "Randy Dunlap" <rdunlap@infradead.org>,
"Christopher Díaz Riveros" <chrisadr@gentoo.org>,
mingo@kernel.org, akpm@linux-foundation.org, tglx@linutronix.de,
keescook@chromium.org, lauraa@codeaurora.org,
rostedt@goodmis.org, mhocko@suse.com, tal.shorer@gmail.com,
viresh.kumar@linaro.org, lokeshvutla@ti.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH-next] init/main.c: make local symbol static
Date: Thu, 18 Jan 2018 16:31:17 -0600 [thread overview]
Message-ID: <30828c91-a39d-6342-2774-32386baa30b6@amd.com> (raw)
In-Reply-To: <9f473c55-7304-dda3-dea4-2734292927a6@infradead.org>
On 1/18/2018 4:09 PM, Randy Dunlap wrote:
> On 01/18/2018 02:06 PM, Christopher Díaz Riveros wrote:
>> Fixes the following sparse warning:
>>
>> init/main.c:167:12: warning:
>> symbol 'envp_init' was not declared. Should it be static?
>>
>> Signed-off-by: Christopher Díaz Riveros <chrisadr@gentoo.org>
>
> Does the kernel build OK after this change?
>
> What about the other user(s) of envp_init?
It looks like it's referenced in init/do_mounts_initrd.c. Rather
than making it static, it should be declared in .h file.
Thanks,
Tom
>
>
>> ---
>> init/main.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/init/main.c b/init/main.c
>> index a8100b954839..ae86addb306c 100644
>> --- a/init/main.c
>> +++ b/init/main.c
>> @@ -164,7 +164,7 @@ static int __init set_reset_devices(char *str)
>> __setup("reset_devices", set_reset_devices);
>>
>> static const char *argv_init[MAX_INIT_ARGS+2] = { "init", NULL, };
>> -const char *envp_init[MAX_INIT_ENVS+2] = { "HOME=/", "TERM=linux", NULL, };
>> +static const char *envp_init[MAX_INIT_ENVS+2] = { "HOME=/", "TERM=linux", NULL, };
>> static const char *panic_later, *panic_param;
>>
>> extern const struct obs_kernel_param __setup_start[], __setup_end[];
>>
>
>
next prev parent reply other threads:[~2018-01-18 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 22:06 Christopher Díaz Riveros
2018-01-18 22:09 ` Randy Dunlap
2018-01-18 22:31 ` Tom Lendacky [this message]
2018-01-18 23:33 ` Christopher Díaz Riveros
2018-01-18 23:35 ` Randy Dunlap
2018-01-19 0:31 ` Steven Rostedt
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=30828c91-a39d-6342-2774-32386baa30b6@amd.com \
--to=thomas.lendacky@amd.com \
--cc=akpm@linux-foundation.org \
--cc=chrisadr@gentoo.org \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tal.shorer@gmail.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®