From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: "Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Cédric Le Goater" <clg@kaod.org>
Subject: linux-next: build warning after merge of the powerpc tree
Date: Mon, 4 Sep 2017 18:53:41 +1000 [thread overview]
Message-ID: <20170904185341.58e3ff62@canb.auug.org.au> (raw)
Hi all,
After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
WARNING: vmlinux.o(.text+0xa7cb8): Section mismatch in reference from the function .xive_spapr_init() to the function .init.text:.xive_core_init()
The function .xive_spapr_init() references
the function __init .xive_core_init().
This is often because .xive_spapr_init lacks a __init
annotation or the annotation of .xive_core_init is wrong.
Introduced by commit
eac1e731b59e ("powerpc/xive: guest exploitation of the XIVE interrupt controller")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-09-04 8:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 8:53 Stephen Rothwell [this message]
2017-09-04 8:59 ` linux-next: build warning after merge of the powerpc tree Cédric Le Goater
-- strict thread matches above, loose matches on Subject: below --
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
2015-10-20 5:21 Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45 ` Stephen Rothwell
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=20170904185341.58e3ff62@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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).