Re: Section mismatch warnings

From: Gabriel C
Date: Tue Jul 31 2007 - 17:58:32 EST


Sam Ravnborg wrote:
> On Tue, Jul 31, 2007 at 09:45:22PM +0200, Gabriel C wrote:
>> Hi Sam ,
>>
>> me again. I got some more mismatch warnings with a randconfig ( http://194.231.229.228/git-current/randconfig-auto-14 )
>>
>>
>> ...
>>
>>
>> MODPOST vmlinux.o
>> WARNING: vmlinux.o(.text+0x8adb): Section mismatch: reference to .init.text:register_cpu (between 'arch_register_cpu' and 'text_poke')
>> WARNING: vmlinux.o(.text+0xb790c): Section mismatch: reference to .init.text:pcibios_fixup_bus (between 'pci_scan_child_bus' and 'pci_scan_bus_parented')
> They need further analysis.

< big snip >

> All the hda_preset stuff should be marked __devinit as far as I can see.
> Care to give that a spin yourself?

Yes.

I'm not sure I can do it today but tomorrow for sure.

>
>> WARNING: vmlinux.o(.data+0xacb10): Section mismatch: reference to .init.text:snd_ad1889_probe (between 'ad1889_pci' and 'ops.20707')
>> WARNING: vmlinux.o(.text+0x12f014): Section mismatch: reference to .exit.text:mlx4_remove_one (between 'mlx4_restart_one' and 'mlx4_cleanup_mcg_table')
> Did not look at these two yet.
>
>> WARNING: vmlinux.o(.init.text+0x29d40): Section mismatch: reference to .exit.text:wbsd_release_resources (between 'wbsd_init' and 'wbsd_probe')
>> WARNING: vmlinux.o(.init.text+0x29d49): Section mismatch: reference to .exit.text:wbsd_free_mmc (between 'wbsd_init' and 'wbsd_probe')
>> WARNING: vmlinux.o(.init.text+0x29f28): Section mismatch: reference to .exit.text:wbsd_free_mmc (between 'wbsd_init' and 'wbsd_probe')
> When a function is marked __exit and used from an init function then the safe choice
> is to just remove the __exit marking. Usually this is small functions used
> only in error situations.
> Should be trivial too.

I'll look at those too

>
> Sorry - no patch this time. Could you try to look at it yorself then I will review.

Ok I'll try.


>
> Sam
>

Gabriel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/