From: kbuild test robot <lkp@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild-all@01.org, linux-kbuild@vger.kernel.org
Subject: [kbuild:build-test2 2/2] WARNING: vmlinux.o(.text.unlikely+0x9cc): Section mismatch in reference from the function check_mult_sh() to the variable .init.data:r4kwar
Date: Sat, 30 Mar 2019 19:21:24 +0800 [thread overview]
Message-ID: <201903301923.eYwt0SS9%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git build-test2
head: 886f44e7cf04e2f591a1744192ad2f47a1640831
commit: 886f44e7cf04e2f591a1744192ad2f47a1640831 [2/2] compiler-attribute: stop forcing __always_inline to inline marker
config: mips-fuloong2e_defconfig (attached as .config)
compiler: mips64el-linux-gnuabi64-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 886f44e7cf04e2f591a1744192ad2f47a1640831
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=mips
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text.unlikely+0x9cc): Section mismatch in reference from the function check_mult_sh() to the variable .init.data:r4kwar
The function check_mult_sh() references
the variable __initdata r4kwar.
This is often because check_mult_sh lacks a __initdata
annotation or the annotation of r4kwar is wrong.
--
>> WARNING: vmlinux.o(.text.unlikely+0x9d0): Section mismatch in reference from the function check_mult_sh() to the variable .init.data:bug64hit
The function check_mult_sh() references
the variable __initdata bug64hit.
This is often because check_mult_sh lacks a __initdata
annotation or the annotation of bug64hit 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: 18219 bytes --]
reply other threads:[~2019-03-30 11:21 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=201903301923.eYwt0SS9%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.masahiro@socionext.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