[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151021074507.46c85604@canb.auug.org.au>
Date: Wed, 21 Oct 2015 07:45:07 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linuxppc-dev@...ts.ozlabs.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org,
Denis Kirjanov <kda@...ux-powerpc.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree
Hi Michael,
On Tue, 20 Oct 2015 21:06:51 +1100 Michael Ellerman <mpe@...erman.id.au> wrote:
>
> On Tue, 2015-10-20 at 16:21 +1100, Stephen Rothwell wrote:
>
> > After merging the powerpc tree, today's linux-next build (powerpc
> > allyesconfig) produced this warning:
> >
> > WARNING: vmlinux.o(.text+0x9367c): Section mismatch in reference from the function .msi_bitmap_alloc() to the function .init.text:.memblock_virt_alloc_try_nid()
> > The function .msi_bitmap_alloc() references
> > the function __init .memblock_virt_alloc_try_nid().
> > This is often because .msi_bitmap_alloc lacks a __init
> > annotation or the annotation of .memblock_virt_alloc_try_nid is wrong.
> >
> > Introduced (probably) by commit
> >
> > cb2d3883c603 ("powerpc/msi: Free the bitmap if it was slab allocated")
>
> Yeah that's correct, though it should be safe in practice.
>
> I'm not sure why you only saw that now though, the patch has been in next since
> the 13th of October.
I don't always notice new warnings immediately among all the others :-(
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists