From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753958AbbJTKG4 (ORCPT ); Tue, 20 Oct 2015 06:06:56 -0400 Received: from ozlabs.org ([103.22.144.67]:58211 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751392AbbJTKGx (ORCPT ); Tue, 20 Oct 2015 06:06:53 -0400 Message-ID: <1445335611.2152.4.camel@ellerman.id.au> Subject: Re: linux-next: build warning after merge of the powerpc tree From: Michael Ellerman To: Stephen Rothwell , Benjamin Herrenschmidt , linuxppc-dev@lists.ozlabs.org Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Denis Kirjanov Date: Tue, 20 Oct 2015 21:06:51 +1100 In-Reply-To: <20151020162155.01391301@canb.auug.org.au> References: <20151020162155.01391301@canb.auug.org.au> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5-1ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2015-10-20 at 16:21 +1100, Stephen Rothwell wrote: > Hi all, > > 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. cheers