From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jason Yan <yanaijie@huawei.com>
Cc: paulburton@kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH] MIPS: Make setup_elfcorehdr and setup_elfcorehdr_size static
Date: Mon, 21 Sep 2020 22:26:00 +0200 [thread overview]
Message-ID: <20200921202600.GE29322@alpha.franken.de> (raw)
In-Reply-To: <20200911020132.1464661-1-yanaijie@huawei.com>
On Fri, Sep 11, 2020 at 10:01:32AM +0800, Jason Yan wrote:
> This addresses the following sparse warning:
>
> arch/mips/kernel/setup.c:446:33: warning: symbol 'setup_elfcorehdr_size'
> was not declared. Should it be static?
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> arch/mips/kernel/setup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-09-21 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 2:01 [PATCH] MIPS: Make setup_elfcorehdr and setup_elfcorehdr_size static Jason Yan
2020-09-21 20:26 ` Thomas Bogendoerfer [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=20200921202600.GE29322@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=hulkci@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=yanaijie@huawei.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;
as well as URLs for NNTP newsgroup(s).