From: kernel test robot <lkp@intel.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Liu Yi L <yi.l.liu@intel.com>
Subject: [luxis1999-iommufd:iommufd-v5.17-rc6 37/40] undefined reference to `iommufd_vfio_check_extension'
Date: Wed, 9 Mar 2022 19:08:39 +0800 [thread overview]
Message-ID: <202203091936.QAP99zL8-lkp@intel.com> (raw)
tree: https://github.com/luxis1999/iommufd iommufd-v5.17-rc6
head: cde3fc107eb3877b1055b6c5cd048c18d6f5b8d5
commit: a3f133279ae994c62f5a14dbcd334564651484c8 [37/40] vfio: Add iommufd VFIO compat support to group_fd
config: microblaze-randconfig-m031-20220308 (https://download.01.org/0day-ci/archive/20220309/202203091936.QAP99zL8-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 11.2.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/luxis1999/iommufd/commit/a3f133279ae994c62f5a14dbcd334564651484c8
git remote add luxis1999-iommufd https://github.com/luxis1999/iommufd
git fetch --no-tags luxis1999-iommufd iommufd-v5.17-rc6
git checkout a3f133279ae994c62f5a14dbcd334564651484c8
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=microblaze 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 >>):
microblaze-linux-ld: drivers/vfio/vfio.o: in function `vfio_external_check_extension':
>> (.text+0x14dc): undefined reference to `iommufd_vfio_check_extension'
microblaze-linux-ld: drivers/vfio/vfio.o: in function `__vfio_group_unset_container':
>> (.text+0x1554): undefined reference to `vfio_group_unset_iommufd'
microblaze-linux-ld: drivers/vfio/vfio.o: in function `vfio_group_set_container':
>> (.text+0x1d50): undefined reference to `vfio_group_set_iommufd'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-09 11:09 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=202203091936.QAP99zL8-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=yi.l.liu@intel.com \
/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