2008-11-21 04:13:44

by Mike Frysinger

Subject: section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip()

WARNING: drivers/mfd/built-in.o(.text+0x8d6): Section mismatch in
reference from the function _sm501_register_gpio() to the function
.devinit.text:_sm501_gpio_register_chip()
The function _sm501_register_gpio() references
the function __devinit _sm501_gpio_register_chip().
This is often because _sm501_register_gpio lacks a __devinit
annotation or the annotation of _sm501_gpio_register_chip is wrong.

WARNING: drivers/mfd/built-in.o(.text+0x90a): Section mismatch in
reference from the function _sm501_register_gpio() to the function
.devinit.text:_sm501_gpio_register_chip()
The function _sm501_register_gpio() references
the function __devinit _sm501_gpio_register_chip().
This is often because _sm501_register_gpio lacks a __devinit
annotation or the annotation of _sm501_gpio_register_chip is wrong.

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
CONFIG_MFD_SM501=y
CONFIG_MFD_SM501_GPIO=y
CONFIG_HTC_PASIC3=y
CONFIG_UCB1400_CORE=m
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_WM8400 is not set
CONFIG_MFD_WM8350=y
CONFIG_MFD_WM8350_I2C=y
-mike

2008-11-24 19:46:42

by Samuel Ortiz

Subject: Re: section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip()

Hi Mike,

On Thu, Nov 20, 2008 at 11:13:31PM -0500, Mike Frysinger wrote:
> WARNING: drivers/mfd/built-in.o(.text+0x8d6): Section mismatch in
> reference from the function _sm501_register_gpio() to the function
> .devinit.text:_sm501_gpio_register_chip()
> The function _sm501_register_gpio() references
> the function __devinit _sm501_gpio_register_chip().
> This is often because _sm501_register_gpio lacks a __devinit
> annotation or the annotation of _sm501_gpio_register_chip is wrong.
>
> WARNING: drivers/mfd/built-in.o(.text+0x90a): Section mismatch in
> reference from the function _sm501_register_gpio() to the function
> .devinit.text:_sm501_gpio_register_chip()
> The function _sm501_register_gpio() references
> the function __devinit _sm501_gpio_register_chip().
> This is often because _sm501_register_gpio lacks a __devinit
> annotation or the annotation of _sm501_gpio_register_chip is wrong.
Which kernel are you triggering this on ?

Cheers,
Samuel.



> #
> # Multifunction device drivers
> #
> # CONFIG_MFD_CORE is not set
> CONFIG_MFD_SM501=y
> CONFIG_MFD_SM501_GPIO=y
> CONFIG_HTC_PASIC3=y
> CONFIG_UCB1400_CORE=m
> # CONFIG_MFD_TMIO is not set
> # CONFIG_MFD_WM8400 is not set
> CONFIG_MFD_WM8350=y
> CONFIG_MFD_WM8350_I2C=y
> -mike

--
Intel Open Source Technology Centre
http://oss.intel.com/

2008-12-18 20:57:19

by Mike Frysinger

Subject: Re: section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip()

On Mon, Nov 24, 2008 at 14:49, Samuel Ortiz wrote:
> On Thu, Nov 20, 2008 at 11:13:31PM -0500, Mike Frysinger wrote:
>> WARNING: drivers/mfd/built-in.o(.text+0x8d6): Section mismatch in
>> reference from the function _sm501_register_gpio() to the function
>> .devinit.text:_sm501_gpio_register_chip()
>> The function _sm501_register_gpio() references
>> the function __devinit _sm501_gpio_register_chip().
>> This is often because _sm501_register_gpio lacks a __devinit
>> annotation or the annotation of _sm501_gpio_register_chip is wrong.
>>
>> WARNING: drivers/mfd/built-in.o(.text+0x90a): Section mismatch in
>> reference from the function _sm501_register_gpio() to the function
>> .devinit.text:_sm501_gpio_register_chip()
>> The function _sm501_register_gpio() references
>> the function __devinit _sm501_gpio_register_chip().
>> This is often because _sm501_register_gpio lacks a __devinit
>> annotation or the annotation of _sm501_gpio_register_chip is wrong.
>
> Which kernel are you triggering this on ?

sorry, i missed this response ... this was in 2.6.28-rc2
-mike