From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: ux500: Silence compiler warnings due to missing __cpuinitdata
Date: Tue, 4 Jun 2013 16:36:48 +0100 [thread overview]
Message-ID: <1370360208-6500-2-git-send-email-lee.jones@linaro.org> (raw)
In-Reply-To: <1370360208-6500-1-git-send-email-lee.jones@linaro.org>
WARNING: vmlinux.o(.text.unlikely+0x25c): Section mismatch in reference \
from the function write_pen_release() to the variable \
.cpuinit.data:pen_release
The function write_pen_release() references
the variable __cpuinitdata pen_release.
This is often because write_pen_release lacks a __cpuinitdata
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
arch/arm/mach-ux500/platsmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-ux500/platsmp.c b/arch/arm/mach-ux500/platsmp.c
index 14d9046..3a455d5 100644
--- a/arch/arm/mach-ux500/platsmp.c
+++ b/arch/arm/mach-ux500/platsmp.c
@@ -34,7 +34,7 @@ extern void u8500_secondary_startup(void);
* observers, irrespective of whether they're taking part in coherency
* or not. This is necessary for the hotplug code to work reliably.
*/
-static void write_pen_release(int val)
+static void __cpuinitdata write_pen_release(int val)
{
pen_release = val;
smp_wmb();
--
1.7.10.4
next prev parent reply other threads:[~2013-06-04 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 15:36 [PATCH 1/2] ARM: ux500: Silence compiler warnings due to missing ux500_read_asicid() __init Lee Jones
2013-06-04 15:36 ` Lee Jones [this message]
2013-06-04 15:57 ` [PATCH 2/2] ARM: ux500: Silence compiler warnings due to missing __cpuinitdata Arnd Bergmann
2013-06-04 16:38 ` Lee Jones
2013-06-04 15:55 ` [PATCH 1/2] ARM: ux500: Silence compiler warnings due to missing ux500_read_asicid() __init Arnd Bergmann
2013-06-05 12:32 ` Linus Walleij
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=1370360208-6500-2-git-send-email-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).