From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: Section mismatch in drivers/mfd/vexpress-sysreg.c
Date: Tue, 29 Jan 2013 13:05:11 +0000 [thread overview]
Message-ID: <1359464711.8090.19.camel@hornet> (raw)
In-Reply-To: <20130129115535.GH21504@S2101-09.ap.freescale.net>
On Tue, 2013-01-29 at 11:55 +0000, Shawn Guo wrote:
> I'm building v3.8-rc5 and seeing the following section mismatch warning
> in drivers/mfd/vexpress-sysreg.c.
>
> WARNING: drivers/mfd/built-in.o(.text+0x3108): Section mismatch in reference from the function vexpress_sysreg_probe() to the function .init.text:vexpress_sysreg_setup()
> The function vexpress_sysreg_probe() references
> the function __init vexpress_sysreg_setup().
> This is often because vexpress_sysreg_probe lacks a __init
> annotation or the annotation of vexpress_sysreg_setup is wrong.
Arnd's got a fix for this already:
https://patchwork.kernel.org/patch/2046991/
Thanks!
Pawel
next prev parent reply other threads:[~2013-01-29 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 11:55 Section mismatch in drivers/mfd/vexpress-sysreg.c Shawn Guo
2013-01-29 12:20 ` Russell King - ARM Linux
2013-01-29 13:05 ` Pawel Moll [this message]
2013-01-29 13:12 ` Russell King - ARM Linux
2013-01-29 18:01 ` Olof Johansson
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=1359464711.8090.19.camel@hornet \
--to=pawel.moll@arm.com \
--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).