From: kernel test robot <lkp@intel.com>
To: steven@liquorix.net
Cc: oe-kbuild-all@lists.linux.dev
Subject: [zen:6.18/zen-sauce 4/29] drivers/pci/controller/intel-nvme-remap.c:47:33: error: field 'sysdata' has incomplete type
Date: Mon, 16 Feb 2026 20:07:26 +0800 [thread overview]
Message-ID: <202602162006.as0bhBeT-lkp@intel.com> (raw)
tree: https://github.com/zen-kernel/zen-kernel 6.18/zen-sauce
head: 0c87fdcd1f9f7f1a09e8928422160159b8966784
commit: dbc40c577cbb482c1d5c92d97724a026113e4526 [4/29] ZEN: PCI: Add Intel remapped NVMe device support
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20260216/202602162006.as0bhBeT-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/20260216/202602162006.as0bhBeT-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/202602162006.as0bhBeT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/pci/controller/intel-nvme-remap.c:47:33: error: field 'sysdata' has incomplete type
47 | struct pci_sysdata sysdata;
| ^~~~~~~
In file included from include/linux/init.h:5,
from include/linux/printk.h:6,
from include/asm-generic/bug.h:22,
from ./arch/um/include/generated/asm/bug.h:1,
from include/linux/bug.h:5,
from include/linux/thread_info.h:13,
from include/asm-generic/preempt.h:5,
from ./arch/um/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from include/linux/spinlock.h:56,
from include/linux/irq.h:14,
from drivers/pci/controller/intel-nvme-remap.c:37:
drivers/pci/controller/intel-nvme-remap.c: In function 'nrdev_from_bus':
include/linux/compiler_types.h:537:27: error: expression in static assertion is not an integer
537 | #define __same_type(a, b) __builtin_types_compatible_p(typeof(a), typeof(b))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:78:56: note: in definition of macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
include/linux/container_of.h:21:9: note: in expansion of macro 'static_assert'
21 | static_assert(__same_type(*(ptr), ((type *)0)->member) || \
| ^~~~~~~~~~~~~
include/linux/container_of.h:21:23: note: in expansion of macro '__same_type'
21 | static_assert(__same_type(*(ptr), ((type *)0)->member) || \
| ^~~~~~~~~~~
drivers/pci/controller/intel-nvme-remap.c:74:16: note: in expansion of macro 'container_of'
74 | return container_of(bus->sysdata, struct nvme_remap_dev, sysdata);
| ^~~~~~~~~~~~
In file included from include/linux/pci.h:44,
from drivers/pci/controller/intel-nvme-remap.c:40:
drivers/pci/controller/intel-nvme-remap.c: At top level:
include/linux/pci_ids.h:23:41: warning: initialized field overwritten [-Woverride-init]
23 | #define PCI_CLASS_STORAGE_RAID 0x0104
| ^~~~~~
drivers/pci/controller/intel-nvme-remap.c:447:26: note: in expansion of macro 'PCI_CLASS_STORAGE_RAID'
447 | .class = PCI_CLASS_STORAGE_RAID << 8,
| ^~~~~~~~~~~~~~~~~~~~~~
include/linux/pci_ids.h:23:41: note: (near initialization for 'nvme_remap_ids[0].class')
23 | #define PCI_CLASS_STORAGE_RAID 0x0104
| ^~~~~~
drivers/pci/controller/intel-nvme-remap.c:447:26: note: in expansion of macro 'PCI_CLASS_STORAGE_RAID'
447 | .class = PCI_CLASS_STORAGE_RAID << 8,
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/pci/controller/intel-nvme-remap.c:448:31: warning: initialized field overwritten [-Woverride-init]
448 | .class_mask = 0xffffff00,
| ^~~~~~~~~~
drivers/pci/controller/intel-nvme-remap.c:448:31: note: (near initialization for 'nvme_remap_ids[0].class_mask')
vim +/sysdata +47 drivers/pci/controller/intel-nvme-remap.c
43
44 struct nvme_remap_dev {
45 struct pci_dev *dev; /* AHCI device */
46 struct pci_bus *bus; /* our fake PCI bus */
> 47 struct pci_sysdata sysdata;
48 int irq_base; /* our fake interrupts */
49
50 /*
51 * When we detect an all-ones write to a BAR register, this flag
52 * is set, so that we return the BAR size on the next read (a
53 * standard PCI behaviour).
54 * This includes the assumption that an all-ones BAR write is
55 * immediately followed by a read of the same register.
56 */
57 bool bar_sizing;
58
59 /*
60 * Resources copied from the AHCI device, to be regarded as
61 * resources on our fake bus.
62 */
63 struct resource ahci_resources[PCI_NUM_RESOURCES];
64
65 /* Resources corresponding to the NVMe devices. */
66 struct resource remapped_dev_mem[AHCI_MAX_REMAP];
67
68 /* Number of remapped NVMe devices found. */
69 int num_remapped_devices;
70 };
71
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-16 12:07 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=202602162006.as0bhBeT-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steven@liquorix.net \
/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.