linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel-bounces@lists.infradead.org,
	Stefan Agner <stefan@agner.ch>
Subject: [PATCH] irqchip/gic-v3: use __init where appropriate
Date: Sat, 29 Dec 2018 15:14:58 +0100	[thread overview]
Message-ID: <478402dd50e3237b14f4d0b41cd945de92de1756.1546092851.git.stefan@agner.ch> (raw)

Compiling with section mismatch debugging enabled prints the
following warning:
  WARNING: vmlinux.o(.text+0xffa1b8): Section mismatch in reference from
  the function gic_smp_init() to the function .init.text:set_smp_cross_call()

Avoid this warning by adding __init to gic_smp_init(). While add it,
also add it where appropriate.

Signed-off-by: Stefan Agner <stefan@agner.ch>
---
 drivers/irqchip/irq-gic-v3.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
index 0868a9d81c3c..3b33c94041e5 100644
--- a/drivers/irqchip/irq-gic-v3.c
+++ b/drivers/irqchip/irq-gic-v3.c
@@ -768,7 +768,7 @@ static void gic_raise_softirq(const struct cpumask *mask, unsigned int irq)
 	isb();
 }
 
-static void gic_smp_init(void)
+static void __init gic_smp_init(void)
 {
 	set_smp_cross_call(gic_raise_softirq);
 	cpuhp_setup_state_nocalls(CPUHP_AP_IRQ_GIC_STARTING,
@@ -848,7 +848,7 @@ static struct notifier_block gic_cpu_pm_notifier_block = {
 	.notifier_call = gic_cpu_pm_notifier,
 };
 
-static void gic_cpu_pm_init(void)
+static void __init gic_cpu_pm_init(void)
 {
 	cpu_pm_register_notifier(&gic_cpu_pm_notifier_block);
 }
-- 
2.20.1


             reply	other threads:[~2018-12-29 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 14:14 Stefan Agner [this message]
2019-01-03 11:08 ` [PATCH] irqchip/gic-v3: use __init where appropriate Marc Zyngier
2019-01-03 13:22   ` Stefan Agner

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=478402dd50e3237b14f4d0b41cd945de92de1756.1546092851.git.stefan@agner.ch \
    --to=stefan@agner.ch \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel-bounces@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=tglx@linutronix.de \
    /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).