From: Masami Hiramatsu <mhiramat@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the ftrace tree
Date: Mon, 25 Oct 2021 15:13:27 +0900 [thread overview]
Message-ID: <20211025151327.00af129d9f876e252b042d01@kernel.org> (raw)
In-Reply-To: <20211025153942.0c31bd06@canb.auug.org.au>
On Mon, 25 Oct 2021 15:39:42 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> WARNING: modpost: vmlinux.o(.text.unlikely+0x90082): Section mismatch in reference from the function xbc_alloc_mem() to the function .init.text:memblock_alloc_try_nid()
> The function xbc_alloc_mem() references
> the function __init memblock_alloc_try_nid().
> This is often because xbc_alloc_mem lacks a __init
> annotation or the annotation of memblock_alloc_try_nid is wrong.
>
> Introduced by commit
>
> 4ee1b4cac236 ("bootconfig: Cleanup dummy headers in tools/bootconfig")
Thanks for reporting!
Let me fix that.
>
> --
> Cheers,
> Stephen Rothwell
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2021-10-25 6:13 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 4:39 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2021-10-25 6:13 ` Masami Hiramatsu [this message]
2021-10-25 8:32 ` [PATCH] lib/bootconfig: Make xbc_alloc_mem() and xbc_free_mem() as __init function Masami Hiramatsu
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 4:35 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2023-06-23 6:53 ` Donglin Peng
2022-11-25 3:10 Stephen Rothwell
2021-10-28 12:23 Stephen Rothwell
2021-10-28 13:16 ` Steven Rostedt
2021-10-28 21:10 ` Stephen Rothwell
2021-10-28 21:29 ` Kalesh Singh
2021-10-28 22:36 ` Stephen Rothwell
2021-10-28 21:30 ` Steven Rostedt
2021-10-25 23:35 Stephen Rothwell
2021-10-26 12:15 ` Masami Hiramatsu
2021-08-23 9:58 Stephen Rothwell
2021-08-23 14:00 ` Steven Rostedt
2021-08-24 10:53 ` Stephen Rothwell
2020-11-16 6:35 Stephen Rothwell
2020-11-16 17:43 ` Steven Rostedt
2020-11-16 19:24 ` Jonathan Corbet
2020-11-16 20:25 ` Steven Rostedt
2020-11-16 20:29 ` Jonathan Corbet
2020-11-16 20:35 ` Steven Rostedt
2020-08-05 4:21 Stephen Rothwell
2019-11-15 3:02 Stephen Rothwell
2019-11-15 3:43 ` Steven Rostedt
2014-06-04 6:09 Stephen Rothwell
2014-06-04 16:26 ` Steven Rostedt
2014-06-04 16:49 ` Stephen Rothwell
2014-06-05 0:20 ` Fengguang Wu
2014-06-05 1:00 ` Steven Rostedt
2014-06-05 1:03 ` Fengguang Wu
2014-06-05 1:12 ` Steven Rostedt
2014-06-05 1:20 ` Steven Rostedt
2014-06-05 1:33 ` Fengguang Wu
2014-06-05 1:39 ` Steven Rostedt
2014-06-05 2:14 ` Fengguang Wu
2014-06-05 2:36 ` Steven Rostedt
2014-06-05 2:50 ` Fengguang Wu
2014-06-05 3:03 ` Fengguang Wu
2014-06-05 3:13 ` Steven Rostedt
2014-06-05 3:42 ` Fengguang Wu
2014-06-05 2:38 ` Steven Rostedt
2014-06-05 2:44 ` Fengguang Wu
2014-06-05 2:46 ` Steven Rostedt
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=20211025151327.00af129d9f876e252b042d01@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.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).