From: kernel test robot <lkp@intel.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: kbuild-all@lists.01.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [linux-nvme:nvme-5.18 4/5] ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined!
Date: Thu, 24 Mar 2022 00:20:47 +0800 [thread overview]
Message-ID: <202203240012.gJehzedI-lkp@intel.com> (raw)
tree: git://git.infradead.org/nvme.git nvme-5.18
head: 84db0c76f3bda283a82c0e883c8f3171048a30bf
commit: ade7dda8539580e02c9004f124783f320924709b [4/5] nvmet: use a private workqueue instead of the system workqueue
config: i386-randconfig-a003 (https://download.01.org/0day-ci/archive/20220324/202203240012.gJehzedI-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
git remote add linux-nvme git://git.infradead.org/nvme.git
git fetch --no-tags linux-nvme nvme-5.18
git checkout ade7dda8539580e02c9004f124783f320924709b
# save the config file to linux build tree
mkdir build_dir
make 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 >>, old ones prefixed by <<):
>> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined!
>> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvme-loop.ko] undefined!
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-03-23 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:20 kernel test robot [this message]
2022-03-23 16:33 ` [linux-nvme:nvme-5.18 4/5] ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined! Sagi Grimberg
2022-03-23 16:33 ` Sagi Grimberg
2022-03-23 16:33 ` Christoph Hellwig
2022-03-23 16:33 ` Christoph Hellwig
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=202203240012.gJehzedI-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=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 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.