On Tue, Dec 11, 2018 at 10:40 AM Ulf Hansson <[email protected]> wrote: > On Mon, 10 Dec 2018 at 23:00, Arnd Bergmann <[email protected]> wrote: > > > > WARNING: vmlinux.o(.text+0x19f90): Section mismatch in reference from the > > function littleton_init_lcd() to the function .init.text:pxa_set_fb_info() > > The function littleton_init_lcd() references > > the function __init pxa_set_fb_info(). > > This is often because littleton_init_lcd lacks a __init > > annotation or the annotation of pxa_set_fb_info is wrong. > > > > WARNING: vmlinux.o(.text+0xf824): Section mismatch in reference from the > > function zeus_register_ohci() to the function .init.text:pxa_set_ohci_info() > > The function zeus_register_ohci() references > > the function __init pxa_set_ohci_info(). > > This is often because zeus_register_ohci lacks a __init > > annotation or the annotation of pxa_set_ohci_info is wrong. > > > > WARNING: vmlinux.o(.text+0xf95c): Section mismatch in reference from the > > function cm_x300_init_u2d() to the function .init.text:pxa3xx_set_u2d_info() > > The function cm_x300_init_u2d() references > > the function __init pxa3xx_set_u2d_info(). > > This is often because cm_x300_init_u2d lacks a __init > > annotation or the annotation of pxa3xx_set_u2d_info is wrong. > > > > Signed-off-by: Arnd Bergmann <[email protected]> > > I have queued a bunch of pxa changes via my mmc tree for gpio > descriptor conversions, by Linus Walleij. > > Are those causing this problem? Should I queue this one via mmc tree as well?
Nopes just correlation without causation... I also made a bunch of patches to PXA through the regulator tree, those are not related either. It *seems* they touch so different code lines that it shouldn't be a problem to merge orthogonally in ARM SoC. Yours, Linus Walleij
