From: kernel test robot <lkp@intel.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Liu Song <liusong@linux.alibaba.com>
Subject: [linux-nvme:nvme-6.8 4/16] ld.lld: error: undefined symbol: nvme_ns_head_ops
Date: Wed, 3 Jan 2024 16:48:45 +0800 [thread overview]
Message-ID: <202401031629.T2JS4GwS-lkp@intel.com> (raw)
tree: git://git.infradead.org/nvme.git nvme-6.8
head: 3b99fc0cd3a7e44fb294d9f6c13173f3dadf4136
commit: 44bc827e396809faa6a4e2dc9bd5f148373ce88b [4/16] nvme: introduce nvme_disk_is_ns_head helper
config: arm-randconfig-001-20240103 (https://download.01.org/0day-ci/archive/20240103/202401031629.T2JS4GwS-lkp@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project baf8a39aaf8b61a38b5b2b5591deb765e42eb00b)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240103/202401031629.T2JS4GwS-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202401031629.T2JS4GwS-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: nvme_ns_head_ops
>>> referenced by sysfs.c
>>> drivers/nvme/host/sysfs.o:(nvme_ns_attrs_are_visible) in archive vmlinux.a
>>> referenced by sysfs.c
>>> drivers/nvme/host/sysfs.o:(nvme_ns_attrs_are_visible) in archive vmlinux.a
>>> referenced by sysfs.c
>>> drivers/nvme/host/sysfs.o:(uuid_show) in archive vmlinux.a
>>> referenced 15 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-03 8:49 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=202401031629.T2JS4GwS-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=liusong@linux.alibaba.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sagi@grimberg.me \
/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