From: kernel test robot <lkp@intel.com>
To: Wei Fu <wefu@redhat.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org,
Palmer Dabbelt <palmer@rivosinc.com>,
Liu Shaohua <liush@allwinnertech.com>,
Guo Ren <guoren@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Subject: [ammarfaizi2-block:palmer/linux/riscv-d1 10/12] WARNING: modpost: vmlinux.o(.text.unlikely+0x1dc): Section mismatch in reference from the function riscv_cpufeature_patch_func() to the function .init.text:cpufeature_probe()
Date: Tue, 8 Mar 2022 19:12:32 +0800 [thread overview]
Message-ID: <202203081902.SJP6xqjp-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block palmer/linux/riscv-d1
head: b3cda759adb0111b5b3efd3a0b986864b647a94a
commit: e1dda1383ff02ab54b09c2173527ee1e79a220ba [10/12] riscv: add RISC-V Svpbmt extension support
config: riscv-defconfig (https://download.01.org/0day-ci/archive/20220308/202203081902.SJP6xqjp-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.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
# https://github.com/ammarfaizi2/linux-block/commit/e1dda1383ff02ab54b09c2173527ee1e79a220ba
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block palmer/linux/riscv-d1
git checkout e1dda1383ff02ab54b09c2173527ee1e79a220ba
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash
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+0x1dc): Section mismatch in reference from the function riscv_cpufeature_patch_func() to the function .init.text:cpufeature_probe()
The function riscv_cpufeature_patch_func() references
the function __init cpufeature_probe().
This is often because riscv_cpufeature_patch_func lacks a __init
annotation or the annotation of cpufeature_probe is wrong.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-08 11:13 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=202203081902.SJP6xqjp-lkp@intel.com \
--to=lkp@intel.com \
--cc=guoren@kernel.org \
--cc=gwml@vger.gnuweeb.org \
--cc=heiko@sntech.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liush@allwinnertech.com \
--cc=palmer@rivosinc.com \
--cc=wefu@redhat.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
all inboxes | Powered by JetHome®