arm: omap3: cm-t3517: fix section mismatch warning

PATCH New Igor Grinberg 2 participants 5 messages Apr 26, 2011 – May 31, 2011

Subsystems (3)

Arm (32-bit) Arm sub-architectures OMAP2+ support

lore

Share & tools

lore

Igor Grinberg

author

2011-04-26 20:41 UTC #0 lore raw

PATCH 1/1 arm: omap3: cm-t3517: fix section mismatch warning

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 <[email protected]>

---
 arch/arm/mach-omap2/board-cm-t3517.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

arch/arm/mach-omap2/board-cm-t3517.c +1 -1

index a27e3ee..802cb60 100644
@@ -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;

Signature · 1 line

1.7.3.4

Igor Grinberg

author

2011-05-03 15:30 UTC #1 lore raw

PATCH 1/1 arm: omap3: cm-t3517: fix section mismatch warning

ping!

Just to make sure you haven't missed this one liner ;)

Quoted 26 lines · Igor Grinberg

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 <[email protected]>
---
 arch/arm/mach-omap2/board-cm-t3517.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
arch/arm/mach-omap2/board-cm-t3517.c +1 -1
index a27e3ee..802cb60 100644
@@ -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;
 

Signature · 2 lines

Regards,
Igor.

Igor Grinberg

author

2011-05-11 07:37 UTC #2 lore raw

PATCH 1/1 arm: omap3: cm-t3517: fix section mismatch warning

ping x2

Can this one get into .39?

Quoted 32 lines · Igor Grinberg

ping!
Just to make sure you haven't missed this one liner ;)
Quoted 26 lines · Igor Grinberg
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 <[email protected]>
---
 arch/arm/mach-omap2/board-cm-t3517.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
arch/arm/mach-omap2/board-cm-t3517.c +1 -1
index a27e3ee..802cb60 100644
@@ -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;
 

Signature · 2 lines

Regards,
Igor.

Igor Grinberg

author

2011-05-16 13:36 UTC #3 lore raw

PATCH 1/1 arm: omap3: cm-t3517: fix section mismatch warning

ping x3

It has been 3 weeks already...

Quoted 40 lines · Igor Grinberg

ping x2
Can this one get into .39?
Quoted 32 lines · Igor Grinberg
ping!
Just to make sure you haven't missed this one liner ;)
Quoted 26 lines · Igor Grinberg
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 <[email protected]>
---
 arch/arm/mach-omap2/board-cm-t3517.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
arch/arm/mach-omap2/board-cm-t3517.c +1 -1
index a27e3ee..802cb60 100644
@@ -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;
 

Signature · 2 lines

Regards,
Igor.

Tony Lindgren

maintainer

2011-05-31 10:36 UTC #4 lore raw

PATCH 1/1 arm: omap3: cm-t3517: fix section mismatch warning

Quoted 19 lines · Igor Grinberg

ping x3
It has been 3 weeks already...
Quoted 11 lines · Igor Grinberg
ping x2
Can this one get into .39?
Quoted 3 lines · Igor Grinberg
ping!
Just to make sure you haven't missed this one liner ;)

For the archives, applying into fixes finally.

Regards,

Tony

Quoted 34 lines

Quoted 29 lines
Quoted 29 lines · Igor Grinberg
Quoted 26 lines
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 <[email protected]>
---
 arch/arm/mach-omap2/board-cm-t3517.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
arch/arm/mach-omap2/board-cm-t3517.c +1 -1
index a27e3ee..802cb60 100644
@@ -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;
 
Signature · 2 lines
Regards,
Igor.