From: ruanjinjie <ruanjinjie@huawei.com>
To: "lkundrak@v3.sk" <lkundrak@v3.sk>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: ruanjinjie <ruanjinjie@huawei.com>
Subject: 答复: [PATCH -next] ARM: mmp: Make mmp2_resource_gpio static
Date: Wed, 14 Sep 2022 06:59:55 +0000 [thread overview]
Message-ID: <aaf1d593d6874c22a2ae56643756e6a6@huawei.com> (raw)
In-Reply-To: <20220901004524.81383-1-ruanjinjie@huawei.com>
Ping.
-----邮件原件-----
发件人: ruanjinjie <ruanjinjie@huawei.com>
发送时间: 2022年9月1日 8:45
收件人: lkundrak@v3.sk; linux@armlinux.org.uk; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org
抄送: ruanjinjie <ruanjinjie@huawei.com>
主题: [PATCH -next] ARM: mmp: Make mmp2_resource_gpio static
The symbol is not used outside of the file, so mark it static.
Fixes the following warning:
./arch/arm/mach-mmp/mmp2.c:157:17: warning: symbol 'mmp2_resource_gpio' was not declared. Should it be static?
Signed-off-by: ruanjinjie <ruanjinjie@huawei.com>
---
arch/arm/mach-mmp/mmp2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mmp/mmp2.c b/arch/arm/mach-mmp/mmp2.c index bbc4c2274de3..696bc1856e6d 100644
--- a/arch/arm/mach-mmp/mmp2.c
+++ b/arch/arm/mach-mmp/mmp2.c
@@ -154,7 +154,7 @@ MMP2_DEVICE(asram, "asram", -1, NONE, 0xe0000000, 0x4000);
/* 0xd1000000 ~ 0xd101ffff is reserved for secure processor */ MMP2_DEVICE(isram, "isram", -1, NONE, 0xd1020000, 0x18000);
-struct resource mmp2_resource_gpio[] = {
+static struct resource mmp2_resource_gpio[] = {
{
.start = 0xd4019000,
.end = 0xd4019fff,
--
2.25.1
next prev parent reply other threads:[~2022-09-14 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 0:45 ruanjinjie
2022-09-14 6:59 ` ruanjinjie [this message]
2022-09-14 7:19 ` Ruan Jinjie
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=aaf1d593d6874c22a2ae56643756e6a6@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
/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®