Section mismatch in drivers/mfd/vexpress-sysreg.c

Section mismatch in drivers/mfd/vexpress-sysreg.c

[Shawn Guo]

Pawel,

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.

Shawn

Section mismatch in drivers/mfd/vexpress-sysreg.c

[Russell King - ARM Linux]

On Tue, Jan 29, 2013 at 07:55:37PM +0800, Shawn Guo wrote:
> Pawel,
> 
> 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.

I've already reported this - it's been around for a while now.

Section mismatch in drivers/mfd/vexpress-sysreg.c

[Pawel Moll]

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

Section mismatch in drivers/mfd/vexpress-sysreg.c

[Russell King - ARM Linux]

On Tue, Jan 29, 2013 at 01:05:11PM +0000, Pawel Moll wrote:
> 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/

Adding arm-soc people...

Which wasn't in yesterday's arm-soc though, as highlighted by last night's
autobuild (the build tree was created at 9:28am yesterday, which'll be
just after my arm-soc pull).

Section mismatch in drivers/mfd/vexpress-sysreg.c

[Olof Johansson]

On Tue, Jan 29, 2013 at 01:12:45PM +0000, Russell King - ARM Linux wrote:
> On Tue, Jan 29, 2013 at 01:05:11PM +0000, Pawel Moll wrote:
> > 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/
> 
> Adding arm-soc people...
> 
> Which wasn't in yesterday's arm-soc though, as highlighted by last night's
> autobuild (the build tree was created at 9:28am yesterday, which'll be
> just after my arm-soc pull).

Right. I checked it in as commit e065d3d417274bafed162b3dffd2e03a5128623c
yesterday, it's in 'fixes' as well as in for-next. It wasn't checked in until
3pm Pacific time though, so it missed your build.

Let me know if it isn't fixed by tonight's build.



-Olof