Re: OMAP totally fucked?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Kevin Hilman <khilman@xxxxxx> [120306 11:13]:
> Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> writes:
> >
> > WARNING: arch/arm/mach-omap2/built-in.o(.text+0x183c): Section mismatch in reference from the function omap2_init_processor_devices() to the function .init.text:_init_omap_device()
> > The function omap2_init_processor_devices() references
> > the function __init _init_omap_device().
> > This is often because omap2_init_processor_devices lacks a __init 
> > annotation or the annotation of _init_omap_device is wrong.
> 
> Below is a fix for this one.
> 
> My compiler (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)) was
> inlining these so I wasn't seeing this warning.  I had to make
> omap2_init_processor_devices() static to make the warning appear.
> 
> Anyways, fix is trivial, patch below.

Thanks, I'll add that to fixes-non-critical-part2.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux