From: kernel test robot <lkp@intel.com>
To: Yishai Hadas <yishaih@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgg@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: [jgunthorpe:for-yishai 14/19] drivers/vfio/pci/mlx5/main.c:519:10: error: 'const struct vfio_device_ops' has no member named 'flags'
Date: Thu, 27 Jan 2022 22:41:42 +0800 [thread overview]
Message-ID: <202201272213.k8dXkt0a-lkp@intel.com> (raw)
tree: https://github.com/jgunthorpe/linux for-yishai
head: 4425468e2b7ec3b986f1ef6aa34a208bb661b2d8
commit: 56686ca194f4c2b4bac10ee8a07080aaeb1a3d03 [14/19] vfio/mlx5: Implement vfio_pci driver for mlx5 devices
config: xtensa-allyesconfig (https://download.01.org/0day-ci/archive/20220127/202201272213.k8dXkt0a-lkp@intel.com/config)
compiler: xtensa-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/jgunthorpe/linux/commit/56686ca194f4c2b4bac10ee8a07080aaeb1a3d03
git remote add jgunthorpe https://github.com/jgunthorpe/linux
git fetch --no-tags jgunthorpe for-yishai
git checkout 56686ca194f4c2b4bac10ee8a07080aaeb1a3d03
# 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=xtensa 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 >>):
>> drivers/vfio/pci/mlx5/main.c:519:10: error: 'const struct vfio_device_ops' has no member named 'flags'
519 | .flags = VFIO_DEV_FLAG_MIG_P2P,
| ^~~~~
>> drivers/vfio/pci/mlx5/main.c:519:18: error: 'VFIO_DEV_FLAG_MIG_P2P' undeclared here (not in a function)
519 | .flags = VFIO_DEV_FLAG_MIG_P2P,
| ^~~~~~~~~~~~~~~~~~~~~
vim +519 drivers/vfio/pci/mlx5/main.c
516
517 static const struct vfio_device_ops mlx5vf_pci_ops = {
518 .name = "mlx5-vfio-pci",
> 519 .flags = VFIO_DEV_FLAG_MIG_P2P,
520 .open_device = mlx5vf_pci_open_device,
521 .close_device = mlx5vf_pci_close_device,
522 .ioctl = vfio_pci_core_ioctl,
523 .device_feature = vfio_pci_core_ioctl_feature,
524 .read = vfio_pci_core_read,
525 .write = vfio_pci_core_write,
526 .mmap = vfio_pci_core_mmap,
527 .request = vfio_pci_core_request,
528 .match = vfio_pci_core_match,
529 .migration_set_state = mlx5vf_pci_set_device_state,
530 };
531
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-27 14:46 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=202201272213.k8dXkt0a-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yishaih@nvidia.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
Powered by JetHome