From: kernel test robot <lkp@intel.com>
To: Chaitanya Kulkarni <kch@nvidia.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: [linux-nvme:nvme-5.18 11/12] ld.lld: error: undefined symbol: nvmet_get_feat_async_event
Date: Mon, 14 Mar 2022 22:23:36 +0800 [thread overview]
Message-ID: <202203142235.GRM0KrZ4-lkp@intel.com> (raw)
tree: git://git.infradead.org/nvme.git nvme-5.18
head: 0ad57fcd030f0bda79a3b6c2fb8fc29b871d9538
commit: 7d36f577e5a3f73768327ca237f444e59140e261 [11/12] nvmet: open code nvmet_get_feat_async_event()
config: i386-randconfig-a016-20220314 (https://download.01.org/0day-ci/archive/20220314/202203142235.GRM0KrZ4-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 3e4950d7fa78ac83f33bbf1658e2f49a73719236)
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 remote add linux-nvme git://git.infradead.org/nvme.git
git fetch --no-tags linux-nvme nvme-5.18
git checkout 7d36f577e5a3f73768327ca237f444e59140e261
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 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 >>):
>> ld.lld: error: undefined symbol: nvmet_get_feat_async_event
>>> referenced by discovery.c:343 (drivers/nvme/target/discovery.c:343)
>>> vmlinux.o:(nvmet_execute_disc_get_features)
>>> did you mean: nvmet_set_feat_async_event
>>> defined in: vmlinux.o
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-14 14:24 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=202203142235.GRM0KrZ4-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=llvm@lists.linux.dev \
/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