From: tip-bot for Geert Uytterhoeven <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, arnd@arndb.de, tglx@linutronix.de,
geert@linux-m68k.org, linux-kernel@vger.kernel.org,
mingo@kernel.org
Subject: [tip:irq/urgent] genirq: Force inlining of __irq_startup_managed to prevent build failure
Date: Tue, 4 Jul 2017 03:40:01 -0700 [thread overview]
Message-ID: <tip-2372a519f63829b8effcdde5f4564a7e036294f0@git.kernel.org> (raw)
In-Reply-To: <1499162761-12398-1-git-send-email-geert@linux-m68k.org>
Commit-ID: 2372a519f63829b8effcdde5f4564a7e036294f0
Gitweb: http://git.kernel.org/tip/2372a519f63829b8effcdde5f4564a7e036294f0
Author: Geert Uytterhoeven <geert@linux-m68k.org>
AuthorDate: Tue, 4 Jul 2017 12:06:01 +0200
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 4 Jul 2017 12:36:44 +0200
genirq: Force inlining of __irq_startup_managed to prevent build failure
If CONFIG_SMP=n, and gcc (e.g. 4.1.2) decides not to inline
__irq_startup_managed(), the build fails with:
kernel/built-in.o: In function `irq_startup':
(.text+0x38ed8): undefined reference to `irq_set_affinity_locked'
Fix this by forcing inlining of __irq_startup_managed().
Fixes: 761ea388e8c4e3ac ("genirq: Handle managed irqs gracefully in irq_startup()")
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Link: http://lkml.kernel.org/r/1499162761-12398-1-git-send-email-geert@linux-m68k.org
---
kernel/irq/chip.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 2e30d925..aa5497d 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -234,7 +234,7 @@ __irq_startup_managed(struct irq_desc *desc, struct cpumask *aff, bool force)
return IRQ_STARTUP_MANAGED;
}
#else
-static int
+static __always_inline int
__irq_startup_managed(struct irq_desc *desc, struct cpumask *aff, bool force)
{
return IRQ_STARTUP_NORMAL;
prev parent reply other threads:[~2017-07-04 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 10:06 [PATCH] " Geert Uytterhoeven
2017-07-04 10:40 ` tip-bot for Geert Uytterhoeven [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-2372a519f63829b8effcdde5f4564a7e036294f0@git.kernel.org \
--to=tipbot@zytor.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--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
all inboxes | Powered by JetHome®