From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Christoph Hellwig <hch@lst.de>
Subject: [linux-next:master 5013/10516] arc-elf-ld: fabrics.c:undefined reference to `nvme_tls_key_lookup'
Date: Tue, 10 Sep 2024 15:37:19 +0800 [thread overview]
Message-ID: <202409101534.Io9V2zBj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 100cc857359b5d731407d1038f7e76cd0e871d94
commit: 5bc46b49c828a6dfaab80b71ecb63fe76a1096d2 [5013/10516] nvme-tcp: check for invalidated or revoked key
config: arc-randconfig-002-20240910 (https://download.01.org/0day-ci/archive/20240910/202409101534.Io9V2zBj-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240910/202409101534.Io9V2zBj-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/202409101534.Io9V2zBj-lkp@intel.com/
All errors (new ones prefixed by >>):
arc-elf-ld: drivers/nvme/host/fabrics.o: in function `nvmf_parse_options':
fabrics.c:(.text+0x1188): undefined reference to `nvme_tls_key_lookup'
>> arc-elf-ld: fabrics.c:(.text+0x1188): undefined reference to `nvme_tls_key_lookup'
arc-elf-ld: fabrics.c:(.text+0x11e0): undefined reference to `nvme_tls_key_lookup'
arc-elf-ld: fabrics.c:(.text+0x11e0): undefined reference to `nvme_tls_key_lookup'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-10 7:38 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=202409101534.Io9V2zBj-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-mm@kvack.org \
--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