From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Denis Kirjanov <kda@linux-powerpc.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree
Date: Tue, 20 Oct 2015 21:06:51 +1100 [thread overview]
Message-ID: <1445335611.2152.4.camel@ellerman.id.au> (raw)
In-Reply-To: <20151020162155.01391301@canb.auug.org.au>
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
next prev parent reply other threads:[~2015-10-20 10:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 5:21 linux-next: build warning after merge of the powerpc tree Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman [this message]
2015-10-20 20:45 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 10:28 Stephen Rothwell
2025-05-29 23:44 ` Stephen Rothwell
2025-05-30 13:10 ` Athira Rajeev
2025-04-29 8:57 Stephen Rothwell
2025-04-29 8:17 Stephen Rothwell
2025-02-19 4:46 Stephen Rothwell
2025-02-19 5:23 ` Madhavan Srinivasan
2025-02-19 5:49 ` Andrew Donnellan
2024-11-20 6:13 Stephen Rothwell
2024-05-15 6:37 Stephen Rothwell
2024-05-16 2:42 ` Michael Ellerman
2024-05-16 4:36 ` Stephen Rothwell
2023-02-16 3:40 Stephen Rothwell
2023-02-16 18:06 ` Josh Poimboeuf
2023-02-17 1:35 ` Michael Ellerman
2023-02-17 7:05 ` Josh Poimboeuf
2021-08-23 9:55 Stephen Rothwell
2021-08-23 10:48 ` Stephen Rothwell
2021-08-23 14:19 ` Jonathan Corbet
2021-08-23 23:21 ` Stephen Rothwell
2021-08-24 5:18 ` Aneesh Kumar K.V
2021-08-24 13:46 ` Jonathan Corbet
2021-04-15 8:52 Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2021-04-14 23:36 Stephen Rothwell
2019-11-13 22:34 Stephen Rothwell
2017-09-04 8:53 Stephen Rothwell
2017-09-04 8:59 ` Cédric Le Goater
2011-05-19 3:19 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1445335611.2152.4.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).