From: kbuild test robot <fengguang.wu@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <mawilcox@microsoft.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [zwisler:ext4_PMD_allocation 41/404] WARNING: mm/built-in.o(.text+0x21122): Section mismatch in reference from the function _get_kmalloc_cache_name() to the variable .init.rodata:_kmalloc_info
Date: Fri, 10 Feb 2017 11:21:59 +0800 [thread overview]
Message-ID: <201702101157.gfuZx7qU%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git ext4_PMD_allocation
head: c0dd530d5927f9bdd798cdfad4842797a58824ac
commit: 3a7f60d64ba4e0c6e96f799f5b93709d963d2495 [41/404] mm, slab: rename kmalloc-node cache to kmalloc-<size>
config: blackfin-allmodconfig (attached as .config)
compiler: bfin-uclinux-gcc (GCC) 6.2.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 3a7f60d64ba4e0c6e96f799f5b93709d963d2495
# save the attached .config to linux build tree
make.cross ARCH=blackfin
All warnings (new ones prefixed by >>):
>> WARNING: mm/built-in.o(.text+0x21122): Section mismatch in reference from the function _get_kmalloc_cache_name() to the variable .init.rodata:_kmalloc_info
The function _get_kmalloc_cache_name() references
the variable __initconst _kmalloc_info.
This is often because _get_kmalloc_cache_name lacks a __initconst
annotation or the annotation of _kmalloc_info 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: 42769 bytes --]
reply other threads:[~2017-02-10 3:22 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=201702101157.gfuZx7qU%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=vbabka@suse.cz \
/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