From: kernel test robot <lkp@intel.com>
To: Guo Ren <guoren@linux.alibaba.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Liu Shaohua <liush@allwinnertech.com>, Wei Fu <wefu@redhat.com>
Subject: [csky-linux:riscv_compat_v6_sv48_xtpbmt 22/22] errata.c:undefined reference to `protection_map'
Date: Mon, 7 Feb 2022 20:44:40 +0800 [thread overview]
Message-ID: <202202072027.HVj3XQyw-lkp@intel.com> (raw)
tree: https://github.com/c-sky/csky-linux riscv_compat_v6_sv48_xtpbmt
head: 660358cf7b5b9fda72e619f37efe4c68af19dccb
commit: 660358cf7b5b9fda72e619f37efe4c68af19dccb [22/22] riscv: errata: pgtable: Add custom Svpbmt supported for Allwinner D1
config: riscv-nommu_virt_defconfig (https://download.01.org/0day-ci/archive/20220207/202202072027.HVj3XQyw-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/c-sky/csky-linux/commit/660358cf7b5b9fda72e619f37efe4c68af19dccb
git remote add csky-linux https://github.com/c-sky/csky-linux
git fetch --no-tags csky-linux riscv_compat_v6_sv48_xtpbmt
git checkout 660358cf7b5b9fda72e619f37efe4c68af19dccb
# 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 errors (new ones prefixed by >>):
riscv64-linux-ld: arch/riscv/errata/thead/errata.o: in function `.L0 ':
>> errata.c:(.init.text+0x28): undefined reference to `protection_map'
>> riscv64-linux-ld: errata.c:(.init.text+0x30): undefined reference to `protection_map'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-07 13:10 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=202202072027.HVj3XQyw-lkp@intel.com \
--to=lkp@intel.com \
--cc=guoren@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liush@allwinnertech.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®