From: kbuild test robot <fengguang.wu@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 186/293] WARNING: mm/built-in.o(.text+0x4f528): Section mismatch in reference from the function section_deactivate() to the function .init.text:section_active_mask.part.3()
Date: Sat, 21 Jan 2017 15:51:07 +0800 [thread overview]
Message-ID: <201701211503.hqt1EiPF%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: fa78008f505569e7988ed3eb737ca7d43d87eac3
commit: 621d4f1abb2f03f3f9521fe4706663ddee531cb4 [186/293] mm: support section-unaligned ZONE_DEVICE memory ranges
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 621d4f1abb2f03f3f9521fe4706663ddee531cb4
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> WARNING: mm/built-in.o(.text+0x4f528): Section mismatch in reference from the function section_deactivate() to the function .init.text:section_active_mask.part.3()
The function section_deactivate() references
the function __init section_active_mask.part.3().
This is often because section_deactivate lacks a __init
annotation or the annotation of section_active_mask.part.3 is wrong.
--
>> WARNING: mm/built-in.o(.meminit.text+0x2311): Section mismatch in reference from the function sparse_add_section() to the function .init.text:section_active_mask.part.3()
The function __meminit sparse_add_section() references
a function __init section_active_mask.part.3().
If section_active_mask.part.3 is only used by sparse_add_section then
annotate section_active_mask.part.3 with a matching annotation.
---
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: 38067 bytes --]
reply other threads:[~2017-01-21 7:51 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=201701211503.hqt1EiPF%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
/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