From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [p2pmem:p2pdma_user_cmb_rfc 15/22] ERROR: modpost: "dma_pci_p2pdma_supported" undefined!
Date: Thu, 29 Oct 2020 07:36:44 +0800 [thread overview]
Message-ID: <202010290742.eyWfj0AG-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
tree: https://github.com/sbates130272/linux-p2pmem.git p2pdma_user_cmb_rfc
head: 3981ac3ce7ad7eb3e904431ebcb219a813555a45
commit: 23e807fe4423086aae72ed747871f6860b704e16 [15/22] nvme-pci: Check DMA ops when indicating support for PCI P2PDMA
config: s390-defconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/sbates130272/linux-p2pmem/commit/23e807fe4423086aae72ed747871f6860b704e16
git remote add p2pmem https://github.com/sbates130272/linux-p2pmem.git
git fetch --no-tags p2pmem p2pdma_user_cmb_rfc
git checkout 23e807fe4423086aae72ed747871f6860b704e16
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390
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: "dma_pci_p2pdma_supported" [drivers/nvme/host/nvme.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 19770 bytes --]
next reply other threads:[~2020-10-28 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 23:36 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-29 3:21 [p2pmem:p2pdma_user_cmb_rfc 15/22] ERROR: modpost: "dma_pci_p2pdma_supported" undefined! kernel 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=202010290742.eyWfj0AG-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.