Re: [PATCH] arm: omap3: cm-t3517: fix section mismatch warning
* Igor Grinberg [110516 06:32]:
> ping x3
>
>
> It has been 3 weeks already...
>
>
> On 05/11/11 10:37, Igor Grinberg wrote:
>
> > ping x2
> >
> >
> > Can this one get into .39?
> >
> >
> > On 05/03/11 18:30, Igor Grinberg wrote:
> >
> >> ping!
> >>
> >> Just to make sure you haven't missed this one liner ;)
For the archives, applying into fixes finally.
Regards,
Tony
> >>
> >>
> >> On 04/26/11 23:41, Igor Grinberg wrote:
> >>> WARNING: arch/arm/mach-omap2/built-in.o(.text+0x11014): Section mismatch
> >>> in reference from the function cm_t3517_init_usbh() to the (unknown
> >>> reference) .init.data:(unknown)
> >>> The function cm_t3517_init_usbh() references
> >>> the (unknown reference) __initdata (unknown).
> >>> This is often because cm_t3517_init_usbh lacks a __initdata
> >>> annotation or the annotation of (unknown) is wrong.
> >>>
> >>> Signed-off-by: Igor Grinberg
> >>> ---
> >>> arch/arm/mach-omap2/board-cm-t3517.c |2 +-
> >>> 1 files changed, 1 insertions(+), 1 deletions(-)
> >>>
> >>> diff --git a/arch/arm/mach-omap2/board-cm-t3517.c
> >>> b/arch/arm/mach-omap2/board-cm-t3517.c
> >>> index a27e3ee..802cb60 100644
> >>> --- a/arch/arm/mach-omap2/board-cm-t3517.c
> >>> +++ b/arch/arm/mach-omap2/board-cm-t3517.c
> >>> @@ -178,7 +178,7 @@ static struct usbhs_omap_board_data
> >>> cm_t3517_ehci_pdata __initdata = {
> >>> .reset_gpio_port[2] = -EINVAL,
> >>> };
> >>>
> >>> -static int cm_t3517_init_usbh(void)
> >>> +static int __init cm_t3517_init_usbh(void)
> >>> {
> >>> int err;
> >>>
>
> --
> Regards,
> Igor.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] arm: omap3: cm-t3517: fix section mismatch warning
ping x3
It has been 3 weeks already...
On 05/11/11 10:37, Igor Grinberg wrote:
> ping x2
>
>
> Can this one get into .39?
>
>
> On 05/03/11 18:30, Igor Grinberg wrote:
>
>> ping!
>>
>> Just to make sure you haven't missed this one liner ;)
>>
>>
>> On 04/26/11 23:41, Igor Grinberg wrote:
>>> WARNING: arch/arm/mach-omap2/built-in.o(.text+0x11014): Section mismatch
>>> in reference from the function cm_t3517_init_usbh() to the (unknown
>>> reference) .init.data:(unknown)
>>> The function cm_t3517_init_usbh() references
>>> the (unknown reference) __initdata (unknown).
>>> This is often because cm_t3517_init_usbh lacks a __initdata
>>> annotation or the annotation of (unknown) is wrong.
>>>
>>> Signed-off-by: Igor Grinberg
>>> ---
>>> arch/arm/mach-omap2/board-cm-t3517.c |2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-omap2/board-cm-t3517.c
>>> b/arch/arm/mach-omap2/board-cm-t3517.c
>>> index a27e3ee..802cb60 100644
>>> --- a/arch/arm/mach-omap2/board-cm-t3517.c
>>> +++ b/arch/arm/mach-omap2/board-cm-t3517.c
>>> @@ -178,7 +178,7 @@ static struct usbhs_omap_board_data cm_t3517_ehci_pdata
>>> __initdata = {
>>> .reset_gpio_port[2] = -EINVAL,
>>> };
>>>
>>> -static int cm_t3517_init_usbh(void)
>>> +static int __init cm_t3517_init_usbh(void)
>>> {
>>> int err;
>>>
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] arm: omap3: cm-t3517: fix section mismatch warning
ping x2
Can this one get into .39?
On 05/03/11 18:30, Igor Grinberg wrote:
> ping!
>
> Just to make sure you haven't missed this one liner ;)
>
>
> On 04/26/11 23:41, Igor Grinberg wrote:
>> WARNING: arch/arm/mach-omap2/built-in.o(.text+0x11014): Section mismatch
>> in reference from the function cm_t3517_init_usbh() to the (unknown
>> reference) .init.data:(unknown)
>> The function cm_t3517_init_usbh() references
>> the (unknown reference) __initdata (unknown).
>> This is often because cm_t3517_init_usbh lacks a __initdata
>> annotation or the annotation of (unknown) is wrong.
>>
>> Signed-off-by: Igor Grinberg
>> ---
>> arch/arm/mach-omap2/board-cm-t3517.c |2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/board-cm-t3517.c
>> b/arch/arm/mach-omap2/board-cm-t3517.c
>> index a27e3ee..802cb60 100644
>> --- a/arch/arm/mach-omap2/board-cm-t3517.c
>> +++ b/arch/arm/mach-omap2/board-cm-t3517.c
>> @@ -178,7 +178,7 @@ static struct usbhs_omap_board_data cm_t3517_ehci_pdata
>> __initdata = {
>> .reset_gpio_port[2] = -EINVAL,
>> };
>>
>> -static int cm_t3517_init_usbh(void)
>> +static int __init cm_t3517_init_usbh(void)
>> {
>> int err;
>>
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] arm: omap3: cm-t3517: fix section mismatch warning
ping!
Just to make sure you haven't missed this one liner ;)
On 04/26/11 23:41, Igor Grinberg wrote:
> WARNING: arch/arm/mach-omap2/built-in.o(.text+0x11014): Section mismatch
> in reference from the function cm_t3517_init_usbh() to the (unknown
> reference) .init.data:(unknown)
> The function cm_t3517_init_usbh() references
> the (unknown reference) __initdata (unknown).
> This is often because cm_t3517_init_usbh lacks a __initdata
> annotation or the annotation of (unknown) is wrong.
>
> Signed-off-by: Igor Grinberg
> ---
> arch/arm/mach-omap2/board-cm-t3517.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-cm-t3517.c
> b/arch/arm/mach-omap2/board-cm-t3517.c
> index a27e3ee..802cb60 100644
> --- a/arch/arm/mach-omap2/board-cm-t3517.c
> +++ b/arch/arm/mach-omap2/board-cm-t3517.c
> @@ -178,7 +178,7 @@ static struct usbhs_omap_board_data cm_t3517_ehci_pdata
> __initdata = {
> .reset_gpio_port[2] = -EINVAL,
> };
>
> -static int cm_t3517_init_usbh(void)
> +static int __init cm_t3517_init_usbh(void)
> {
> int err;
>
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
