From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android17-6.18-lts 7/7] /usr/bin/ld: tools/testing/selftests/vfio/lib/vfio_pci_driver.o:undefined reference to `ioat_ops'
Date: Mon, 16 Nov 2026 10:58:37 +0100 [thread overview]
Message-ID: <202611161055.IOLqrwIQ-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com
Hi David,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android17-6.18-lts
head: 44c4d19047cd3c9c51c6fa3930c35844b10b5f9a
commit: 2223587df5c5e935cc6f973f62a9608eef81bec8 [7/7] vfio: selftests: Add driver for Intel CBDMA
:::::: branch date: 18 hours ago
:::::: commit date: 1 year, 3 months ago
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261116/202611161055.IOLqrwIQ-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261116/202611161055.IOLqrwIQ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Fixes: 2223587df5c5 ("vfio: selftests: Add driver for Intel CBDMA")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202611161055.IOLqrwIQ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> /usr/bin/ld: tools/testing/selftests/vfio/lib/vfio_pci_driver.o:(.data.rel+0x0): undefined reference to `ioat_ops'
collect2: error: ld returned 1 exit status
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-16 9:59 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=202611161055.IOLqrwIQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.