From: kernel test robot <lkp@intel.com>
To: Zong Li <zong.li@sifive.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Anup Patel <anup@brainfault.org>
Subject: tnc.c:undefined reference to `ubifs_bad_hash'
Date: Thu, 10 Dec 2020 15:01:11 +0800 [thread overview]
Message-ID: <202012101507.INABZDI3-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a2f5ea9e314ba6778f885c805c921e9362ec0420
commit: 0da310e82d3a9bff6ef6b0f2fbf45d1a05cc64fe riscv: gcov: enable gcov for RISC-V
date: 11 months ago
config: riscv-randconfig-r003-20201209 (attached as .config)
compiler: riscv32-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
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0da310e82d3a9bff6ef6b0f2fbf45d1a05cc64fe
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 0da310e82d3a9bff6ef6b0f2fbf45d1a05cc64fe
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
riscv32-linux-ld: fs/ubifs/tnc.o: in function `.L345':
>> tnc.c:(.text+0x4c9c): undefined reference to `ubifs_bad_hash'
riscv32-linux-ld: fs/ubifs/tnc.o: in function `.L362':
tnc.c:(.text+0x544a): undefined reference to `ubifs_bad_hash'
riscv32-linux-ld: fs/ubifs/tnc_misc.o: in function `.L36':
>> tnc_misc.c:(.text+0x778): undefined reference to `ubifs_bad_hash'
riscv32-linux-ld: fs/ubifs/tnc_misc.o: in function `.L187':
tnc_misc.c:(.text+0x2cce): undefined reference to `ubifs_bad_hash'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25040 bytes --]
reply other threads:[~2020-12-10 7:02 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=202012101507.INABZDI3-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.walmsley@sifive.com \
--cc=zong.li@sifive.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