From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jirislaby:devel 52/76] WARNING: modpost: vmlinux.o(.text.unlikely+0x7a4): Section mismatch in reference from the variable $L95 to the variable .init.data:l1parity
Date: Wed, 17 Jun 2020 21:23:59 +0800 [thread overview]
Message-ID: <202006172155.6Js4FuXT%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4164 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head: bf8fd3c80f466d63067fd6a6f31ef0fbb332c20c
commit: 4ec87cb7efaeec51cc6867baadb16b484f88a938 [52/76] include condition in the BUG_ON/WARN_ON output
config: mips-malta_qemu_32r6_defconfig (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 4ec87cb7efaeec51cc6867baadb16b484f88a938
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x7a4): Section mismatch in reference from the variable $L95 to the variable .init.data:l1parity
The function $L95() references
the variable __initdata l1parity.
This is often because $L95 lacks a __initdata
annotation or the annotation of l1parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x83c): Section mismatch in reference from the variable $L98 to the variable .init.data:l1parity
The function $L98() references
the variable __initdata l1parity.
This is often because $L98 lacks a __initdata
annotation or the annotation of l1parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x850): Section mismatch in reference from the variable $L98 to the variable .init.data:l2parity
The function $L98() references
the variable __initdata l2parity.
This is often because $L98 lacks a __initdata
annotation or the annotation of l2parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x878): Section mismatch in reference from the variable $L104 to the variable .init.data:l2parity
The function $L104() references
the variable __initdata l2parity.
This is often because $L104 lacks a __initdata
annotation or the annotation of l2parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x8e8): Section mismatch in reference from the variable $L109 to the variable .init.data:l1parity
The function $L109() references
the variable __initdata l1parity.
This is often because $L109 lacks a __initdata
annotation or the annotation of l1parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x6e0): Section mismatch in reference from the variable $L88 to the variable .init.data:l2parity
The function $L88() references
the variable __initdata l2parity.
This is often because $L88 lacks a __initdata
annotation or the annotation of l2parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x6ec): Section mismatch in reference from the variable $L89 to the variable .init.data:l1parity
The function $L89() references
the variable __initdata l1parity.
This is often because $L89 lacks a __initdata
annotation or the annotation of l1parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x704): Section mismatch in reference from the variable $L91 to the variable .init.data:l1parity
The function $L91() references
the variable __initdata l1parity.
This is often because $L91 lacks a __initdata
annotation or the annotation of l1parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x73c): Section mismatch in reference from the variable $L92 to the variable .init.data:l2parity
The function $L92() references
the variable __initdata l2parity.
This is often because $L92 lacks a __initdata
annotation or the annotation of l2parity is wrong.
--
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x76c): Section mismatch in reference from the variable $L94 to the variable .init.data:l2parity
The function $L94() references
the variable __initdata l2parity.
This is often because $L94 lacks a __initdata
annotation or the annotation of l2parity is wrong.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 16817 bytes --]
reply other threads:[~2020-06-17 13:23 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=202006172155.6Js4FuXT%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.