radio: fix sf16fmi section mismatch
PATCH 1/1 radio: fix sf16fmi section mismatch
From: Randy Dunlap <[email protected]>
isapnp_fmi_probe() is only called by fmi_init(), which is __init, so isapnp_fmi_probe() can also be __init.
media/radio/radio-sf16fmi.c:
WARNING: vmlinux.o(.text+0x994e19): Section mismatch: reference to .init.data: (between 'isapnp_fmi_probe' and 'vidioc_s_tuner')
WARNING: vmlinux.o(.text+0x994e22): Section mismatch: reference to .init.data: (between 'isapnp_fmi_probe' and 'vidioc_s_tuner')
WARNING: vmlinux.o(.text+0x994e3a): Section mismatch: reference to .init.data:id_table (between 'isapnp_fmi_probe' and 'vidioc_s_tuner')
--- drivers/media/radio/radio-sf16fmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/radio/radio-sf16fmi.c +1 -1
@@ -321,7 +321,7 @@ static struct isapnp_device_id id_table[MODULE_DEVICE_TABLE (isapnp, id_table); -static int isapnp_fmi_probe (void ) +static int __init isapnp_fmi_probe (void ) {int i =0 ;
Quoted 11 lines · Randy Dunlap
From: Randy Dunlap <[email protected]>
isapnp_fmi_probe()is only called byfmi_init(), which is__init, soisapnp_fmi_probe()can also be__init.
media/radio/radio-sf16fmi.c:
WARNING:vmlinux.o(.text+0x994e19): Section mismatch: reference to .init.data: (between 'isapnp_fmi_probe' and 'vidioc_s_tuner')
WARNING:vmlinux.o(.text+0x994e22): Section mismatch: reference to .init.data: (between 'isapnp_fmi_probe' and 'vidioc_s_tuner')
WARNING:vmlinux.o(.text+0x994e3a): Section mismatch: reference to .init.data:id_table (between 'isapnp_fmi_probe' and 'vidioc_s_tuner')Signed-off-by Randy Dunlap <[email protected]>
Quoted 20 lines
--- drivers/media/radio/radio-sf16fmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/media/radio/radio-sf16fmi.c +1
-2@@ -321,7 +321,7 @@ static struct isapnp_device_id id_table[MODULE_DEVICE_TABLE (isapnp, id_table); -static int isapnp_fmi_probe (void ) +static int __init isapnp_fmi_probe (void ) {int i =0 ; --To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/