From: kbuild test robot <fengguang.wu@intel.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
Steven Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Bob Picco <bob.picco@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6243/6567] WARNING: vmlinux.o(.text+0x110b34): Section mismatch in reference from the function deferred_init_range() to the function .init.text:deferred_free_range()
Date: Wed, 18 Oct 2017 09:36:07 +0800 [thread overview]
Message-ID: <201710180905.dfBlUI5y%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: a7dd40274d75326ca868479c62090b1198a357ad
commit: 430676b385fb341d5a33950bae284d0df2e70117 [6243/6567] mm: deferred_init_memmap improvements
config: x86_64-randconfig-v0-10180807 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout 430676b385fb341d5a33950bae284d0df2e70117
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text+0x110b34): Section mismatch in reference from the function deferred_init_range() to the function .init.text:deferred_free_range()
The function deferred_init_range() references
the function __init deferred_free_range().
This is often because deferred_init_range lacks a __init
annotation or the annotation of deferred_free_range is wrong.
--
>> WARNING: vmlinux.o(.text+0x110bc0): Section mismatch in reference from the function deferred_init_range() to the function .meminit.text:__init_single_page()
The function deferred_init_range() references
the function __meminit __init_single_page().
This is often because deferred_init_range lacks a __meminit
annotation or the annotation of __init_single_page is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 21911 bytes --]
reply other threads:[~2017-10-18 1:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201710180905.dfBlUI5y%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bob.picco@oracle.com \
--cc=broonie@kernel.org \
--cc=daniel.m.jordan@oracle.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@oracle.com \
--cc=steven.sistare@oracle.com \
/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).