From: "tip-bot2 for Jason Yan" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Hulk Robot <hulkci@huawei.com>, Jason Yan <yanaijie@huawei.com>,
Marc Zyngier <maz@kernel.org>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: irq/urgent] irqchip/irq-mvebu-icu: Make legacy_bindings static
Date: Fri, 17 Apr 2020 09:56:43 -0000 [thread overview]
Message-ID: <158711740334.28353.7285300834991245174.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200417074046.46771-1-yanaijie@huawei.com>
The following commit has been merged into the irq/urgent branch of tip:
Commit-ID: 9fed9ccb16de9b18ba843d2df57312c9b8260f96
Gitweb: https://git.kernel.org/tip/9fed9ccb16de9b18ba843d2df57312c9b8260f96
Author: Jason Yan <yanaijie@huawei.com>
AuthorDate: Fri, 17 Apr 2020 15:40:46 +08:00
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Fri, 17 Apr 2020 08:59:29 +01:00
irqchip/irq-mvebu-icu: Make legacy_bindings static
Fix the following sparse warning:
drivers/irqchip/irq-mvebu-icu.c:69:1: warning: symbol 'legacy_bindings'
was not declared. Should it be static?
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Jason Yan <yanaijie@huawei.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20200417074046.46771-1-yanaijie@huawei.com
---
drivers/irqchip/irq-mvebu-icu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-mvebu-icu.c b/drivers/irqchip/irq-mvebu-icu.c
index 547045d..91adf77 100644
--- a/drivers/irqchip/irq-mvebu-icu.c
+++ b/drivers/irqchip/irq-mvebu-icu.c
@@ -66,7 +66,7 @@ struct mvebu_icu_irq_data {
unsigned int type;
};
-DEFINE_STATIC_KEY_FALSE(legacy_bindings);
+static DEFINE_STATIC_KEY_FALSE(legacy_bindings);
static void mvebu_icu_init(struct mvebu_icu *icu,
struct mvebu_icu_msi_data *msi_data,
prev parent reply other threads:[~2020-04-17 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 7:40 [PATCH] irqchip/irq-mvebu-icu: make legacy_bindings static Jason Yan
2020-04-17 9:56 ` tip-bot2 for Jason Yan [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=158711740334.28353.7285300834991245174.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=hulkci@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=maz@kernel.org \
--cc=x86@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).