From: kernel test robot <lkp@intel.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Jon Mason <jdmason@kudzu.us>
Subject: [linux-next:master 3951/5720] drivers/pci/endpoint/functions/pci-epf-vntb.c:1247: undefined reference to `ntb_register_device'
Date: Sun, 26 Jun 2022 05:42:07 +0800 [thread overview]
Message-ID: <202206260540.XO9lsEPW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2f9cb3d3bd73fc2225d66aa8fcffb632ed3eb235
commit: ff32fac00d97661c715ee47bbfd867cae1f3aaf8 [3951/5720] NTB: EPF: support NTB transfer between PCI RC and EP connection
config: parisc-randconfig-c003-20220626
compiler: hppa-linux-gcc (GCC) 11.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ff32fac00d97661c715ee47bbfd867cae1f3aaf8
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout ff32fac00d97661c715ee47bbfd867cae1f3aaf8
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
hppa-linux-ld: drivers/pci/endpoint/functions/pci-epf-vntb.o: in function `pci_vntb_probe':
>> drivers/pci/endpoint/functions/pci-epf-vntb.c:1247: undefined reference to `ntb_register_device'
hppa-linux-ld: drivers/pci/endpoint/functions/pci-epf-vntb.o: in function `epf_ntb_cmd_handler':
>> drivers/pci/endpoint/functions/pci-epf-vntb.c:262: undefined reference to `ntb_db_event'
hppa-linux-ld: drivers/pci/endpoint/functions/pci-epf-vntb.o: in function `epf_ntb_link_up':
>> drivers/pci/endpoint/functions/pci-epf-vntb.c:174: undefined reference to `ntb_link_event'
vim +1247 drivers/pci/endpoint/functions/pci-epf-vntb.c
1230
1231 static int pci_vntb_probe(struct pci_dev *pdev, const struct pci_device_id *id)
1232 {
1233 int ret;
1234 struct epf_ntb *ndev = (struct epf_ntb *)pdev->sysdata;
1235 struct device *dev = &pdev->dev;
1236
1237 ndev->ntb.pdev = pdev;
1238 ndev->ntb.topo = NTB_TOPO_NONE;
1239 ndev->ntb.ops = &vntb_epf_ops;
1240
1241 ret = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32));
1242 if (ret) {
1243 dev_err(dev, "Cannot set DMA mask\n");
1244 return -1;
1245 }
1246
> 1247 ret = ntb_register_device(&ndev->ntb);
1248 if (ret) {
1249 dev_err(dev, "Failed to register NTB device\n");
1250 goto err_register_dev;
1251 }
1252
1253 dev_info(dev, "PCI Virtual NTB driver loaded\n");
1254 return 0;
1255
1256 err_register_dev:
1257 return -1;
1258 }
1259
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-25 21:42 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=202206260540.XO9lsEPW-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=jdmason@kudzu.us \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox