From: kernel test robot <lkp@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kevin Tian <kevin.tian@intel.com>,
Alex Williamson <alex@shazbot.org>
Subject: [linux-next:master 12337/13055] drivers/vfio/pci/xe/main.c:555:2: error: call to undeclared function 'INTEL_WCL_IDS'; ISO C99 and later do not support implicit function declarations
Date: Wed, 3 Dec 2025 09:15:57 +0800 [thread overview]
Message-ID: <202512030951.SoXeWc1k-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 47b7b5e32bb7264b51b89186043e1ada4090b558
commit: 2e38c50ae4929f0b954fee69d428db7121452867 [12337/13055] vfio/xe: Add device specific vfio_pci driver variant for Intel graphics
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20251203/202512030951.SoXeWc1k-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251203/202512030951.SoXeWc1k-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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512030951.SoXeWc1k-lkp@intel.com/
Note: the linux-next/master HEAD 47b7b5e32bb7264b51b89186043e1ada4090b558 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> drivers/vfio/pci/xe/main.c:555:2: error: call to undeclared function 'INTEL_WCL_IDS'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
555 | INTEL_WCL_IDS(INTEL_PCI_VFIO_DEVICE),
| ^
drivers/vfio/pci/xe/main.c:555:16: error: use of undeclared identifier 'INTEL_PCI_VFIO_DEVICE'
555 | INTEL_WCL_IDS(INTEL_PCI_VFIO_DEVICE),
| ^
>> drivers/vfio/pci/xe/main.c:559:1: error: definition of variable with array type needs an explicit size or an initializer
559 | MODULE_DEVICE_TABLE(pci, xe_vfio_pci_table);
| ^
include/linux/module.h:261:21: note: expanded from macro 'MODULE_DEVICE_TABLE'
261 | static typeof(name) __mod_device_table(type, name) \
| ^
include/linux/module.h:253:2: note: expanded from macro '__mod_device_table'
253 | __PASTE(__mod_device_table__, \
| ^
include/linux/compiler_types.h:84:22: note: expanded from macro '__PASTE'
84 | #define __PASTE(a,b) ___PASTE(a,b)
| ^
include/linux/compiler_types.h:83:23: note: expanded from macro '___PASTE'
83 | #define ___PASTE(a,b) a##b
| ^
<scratch space>:152:1: note: expanded from here
152 | __mod_device_table__kmod_xe_vfio_pci__pci__xe_vfio_pci_table
| ^
3 errors generated.
vim +/INTEL_WCL_IDS +555 drivers/vfio/pci/xe/main.c
552
553 static const struct pci_device_id xe_vfio_pci_table[] = {
554 INTEL_PTL_IDS(INTEL_PCI_VFIO_DEVICE),
> 555 INTEL_WCL_IDS(INTEL_PCI_VFIO_DEVICE),
556 INTEL_BMG_IDS(INTEL_PCI_VFIO_DEVICE),
557 {}
558 };
> 559 MODULE_DEVICE_TABLE(pci, xe_vfio_pci_table);
560
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-03 1:17 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=202512030951.SoXeWc1k-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@shazbot.org \
--cc=kevin.tian@intel.com \
--cc=llvm@lists.linux.dev \
--cc=michal.winiarski@intel.com \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox