From: kbuild test robot <lkp@intel.com>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Jens Axboe" <axboe@kernel.dk>,
"Javier González" <javier@cnexlabs.com>
Subject: ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefined!
Date: Tue, 30 Oct 2018 18:17:32 +0800 [thread overview]
Message-ID: <201810301828.5IfRf5z6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
Hi Matias,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 11743c56785c751c087eecdb98713eef796609e0
commit: 73569e11032fc5a9b314b6351632cfca7793afd5 lightnvm: remove dependencies on BLK_DEV_NVME and PCI
date: 3 weeks ago
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 73569e11032fc5a9b314b6351632cfca7793afd5
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=ia64
All errors (new ones prefixed by >>):
ERROR: "ia64_delay_loop" [drivers/spi/spi-thunderx.ko] undefined!
>> ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefined!
ERROR: "__sw_hweight8" [drivers/net/wireless/mediatek/mt76/mt76.ko] undefined!
ERROR: "ia64_delay_loop" [drivers/net/phy/mdio-cavium.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 51861 bytes --]
next reply other threads:[~2018-10-30 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 10:17 kbuild test robot [this message]
2018-10-31 4:43 ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefined! kbuild test robot
2018-11-01 11:35 kbuild test robot
2018-11-20 5:12 kbuild test robot
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=201810301828.5IfRf5z6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=javier@cnexlabs.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
/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;
as well as URLs for NNTP newsgroup(s).