From: tip-bot for YueHaibing <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, marc.zyngier@arm.com, yuehaibing@huawei.com,
andrew@lunn.ch, mingo@kernel.org,
sebastian.hesselbarth@gmail.com,
linux-arm-kernel@lists.infradead.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, gregory.clement@bootlin.com,
jason@lakedaemon.net
Subject: [tip:irq/urgent] irqchip/irq-mvebu-sei: Make mvebu_sei_ap806_caps static
Date: Thu, 21 Mar 2019 08:46:17 -0700 [thread overview]
Message-ID: <tip-f27b744baaa646a7c0a01443cc0d8b4787cac2f7@git.kernel.org> (raw)
In-Reply-To: <20190321151448.15600-1-yuehaibing@huawei.com>
Commit-ID: f27b744baaa646a7c0a01443cc0d8b4787cac2f7
Gitweb: https://git.kernel.org/tip/f27b744baaa646a7c0a01443cc0d8b4787cac2f7
Author: YueHaibing <yuehaibing@huawei.com>
AuthorDate: Thu, 21 Mar 2019 23:14:48 +0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 21 Mar 2019 16:43:00 +0100
irqchip/irq-mvebu-sei: Make mvebu_sei_ap806_caps static
Fix sparse warning:
drivers/irqchip/irq-mvebu-sei.c:481:23: warning:
symbol 'mvebu_sei_ap806_caps' was not declared. Should it be static?
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: <jason@lakedaemon.net>
Cc: <andrew@lunn.ch>
Cc: <gregory.clement@bootlin.com>
Cc: <sebastian.hesselbarth@gmail.com>
Cc: <marc.zyngier@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>
Link: https://lkml.kernel.org/r/20190321151448.15600-1-yuehaibing@huawei.com
---
drivers/irqchip/irq-mvebu-sei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-mvebu-sei.c b/drivers/irqchip/irq-mvebu-sei.c
index add4c9c934c8..18832ccc8ff8 100644
--- a/drivers/irqchip/irq-mvebu-sei.c
+++ b/drivers/irqchip/irq-mvebu-sei.c
@@ -478,7 +478,7 @@ dispose_irq:
return ret;
}
-struct mvebu_sei_caps mvebu_sei_ap806_caps = {
+static struct mvebu_sei_caps mvebu_sei_ap806_caps = {
.ap_range = {
.first = 0,
.size = 21,
prev parent reply other threads:[~2019-03-21 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 15:14 [PATCH -next] " Yue Haibing
2019-03-21 15:46 ` tip-bot for YueHaibing [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=tip-f27b744baaa646a7c0a01443cc0d8b4787cac2f7@git.kernel.org \
--to=tipbot@zytor.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
--cc=yuehaibing@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
all inboxes | Powered by JetHome®