From: kernel test robot <lkp@intel.com>
To: Will Deacon <will@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [arm-perf:kvm/bpf 2/3] ERROR: modpost: "bpf_base_func_proto" [arch/riscv/kvm/kvm.ko] undefined!
Date: Wed, 7 Jun 2023 19:27:01 +0800 [thread overview]
Message-ID: <202306071938.yVCAVTFl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git kvm/bpf
head: 044975299633da153eec3842998426f5f93cda92
commit: bb22c4e9bcd0289f0ec15ddbf04e8f1e4289fc09 [2/3] KVM: Add support for new KVM_DEV_TYPE_BPF device
config: riscv-defconfig (https://download.01.org/0day-ci/archive/20230607/202306071938.yVCAVTFl-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build):
mkdir -p ~/bin
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/will/linux.git/commit/?id=bb22c4e9bcd0289f0ec15ddbf04e8f1e4289fc09
git remote add arm-perf https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git
git fetch --no-tags arm-perf kvm/bpf
git checkout bb22c4e9bcd0289f0ec15ddbf04e8f1e4289fc09
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=riscv olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306071938.yVCAVTFl-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "bpf_base_func_proto" [arch/riscv/kvm/kvm.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-07 11:29 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=202306071938.yVCAVTFl-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=will@kernel.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.