From: kernel test robot <yujie.liu@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Keith Busch" <kbusch@kernel.org>, Hannes Reinecke <hare@suse.de>,
Christoph Hellwig <hch@lst.de>
Subject: tcp.c:undefined reference to `nvme_tls_psk_default'
Date: Tue, 14 Nov 2023 15:56:22 +0800 [thread overview]
Message-ID: <202311140426.0eHrTXBr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9bacdd8996c77c42ca004440be610692275ff9d0
commit: 6affe08aea5f3b630565676e227b41d55a6f009c nvme: common: make keyring and auth separate modules
date: 6 days ago
config: csky-randconfig-002-20231114 (https://download.01.org/0day-ci/archive/20231114/202311140426.0eHrTXBr-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231114/202311140426.0eHrTXBr-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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202311140426.0eHrTXBr-lkp@intel.com/
All errors (new ones prefixed by >>):
csky-linux-ld: drivers/nvme/host/core.o: in function `nvme_core_init':
core.c:(.init.text+0xa0): undefined reference to `nvme_keyring_init'
csky-linux-ld: core.c:(.init.text+0x130): undefined reference to `nvme_keyring_init'
csky-linux-ld: drivers/nvme/host/tcp.o: in function `nvme_tcp_configure_admin_queue':
>> tcp.c:(.text+0x2f8a): undefined reference to `nvme_tls_psk_default'
>> csky-linux-ld: tcp.c:(.text+0x3088): undefined reference to `nvme_tls_psk_default'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-14 8:02 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=202311140426.0eHrTXBr-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=arnd@arndb.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®