From: kernel test robot <lkp@intel.com>
To: Yi Liu <yi.l.liu@intel.com>, Kevin Tian <kevin.tian@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [yiliu1765-iommufd:wip/iommufd_pasid 68/70] drivers/vfio/pci/vfio_pci.c:145:35: error: 'vfio_iommufd_physical_pasid_attach_ioas' undeclared here (not in a function); did you mean 'vfio_iommufd_physical_attach_ioas'?
Date: Wed, 12 Jul 2023 18:43:31 +0800 [thread overview]
Message-ID: <202307121817.8ldDJAZF-lkp@intel.com> (raw)
tree: https://github.com/yiliu1765/iommufd.git wip/iommufd_pasid
head: 8db4af69ff01c9d7e21e41bf884c6c727dd8525a
commit: 3ec6edc4643d8e526bbcd6eff007c2c6e15383ee [68/70] vfio-iommufd: Support pasid [at|de]tach for physical VFIO devices
config: s390-defconfig (https://download.01.org/0day-ci/archive/20230712/202307121817.8ldDJAZF-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230712/202307121817.8ldDJAZF-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/202307121817.8ldDJAZF-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/vfio/pci/vfio_pci.c:145:35: error: 'vfio_iommufd_physical_pasid_attach_ioas' undeclared here (not in a function); did you mean 'vfio_iommufd_physical_attach_ioas'?
145 | .pasid_attach_ioas = vfio_iommufd_physical_pasid_attach_ioas,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| vfio_iommufd_physical_attach_ioas
>> drivers/vfio/pci/vfio_pci.c:146:35: error: 'vfio_iommufd_physical_pasid_detach_ioas' undeclared here (not in a function); did you mean 'vfio_iommufd_physical_detach_ioas'?
146 | .pasid_detach_ioas = vfio_iommufd_physical_pasid_detach_ioas,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| vfio_iommufd_physical_detach_ioas
vim +145 drivers/vfio/pci/vfio_pci.c
127
128 static const struct vfio_device_ops vfio_pci_ops = {
129 .name = "vfio-pci",
130 .init = vfio_pci_core_init_dev,
131 .release = vfio_pci_core_release_dev,
132 .open_device = vfio_pci_open_device,
133 .close_device = vfio_pci_core_close_device,
134 .ioctl = vfio_pci_core_ioctl,
135 .device_feature = vfio_pci_core_ioctl_feature,
136 .read = vfio_pci_core_read,
137 .write = vfio_pci_core_write,
138 .mmap = vfio_pci_core_mmap,
139 .request = vfio_pci_core_request,
140 .match = vfio_pci_core_match,
141 .bind_iommufd = vfio_iommufd_physical_bind,
142 .unbind_iommufd = vfio_iommufd_physical_unbind,
143 .attach_ioas = vfio_iommufd_physical_attach_ioas,
144 .detach_ioas = vfio_iommufd_physical_detach_ioas,
> 145 .pasid_attach_ioas = vfio_iommufd_physical_pasid_attach_ioas,
> 146 .pasid_detach_ioas = vfio_iommufd_physical_pasid_detach_ioas,
147 };
148
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-12 10:43 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=202307121817.8ldDJAZF-lkp@intel.com \
--to=lkp@intel.com \
--cc=kevin.tian@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.