Hi Yan, [FYI, it's a private test report for your RFC patch.] [auto build test WARNING on vfio/next] [also build test WARNING on jkirsher-next-queue/dev-queue linus/master v5.7-rc6 next-20200515] [cannot apply to linux/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Yan-Zhao/Introduce-vendor-ops-in... base: https://github.com/awilliam/linux-vfio.git next config: x86_64-allyesconfig (attached as .config) reproduce: # apt-get install sparse # sparse version: v0.6.1-193-gb8fad4bc-dirty # save the attached .config to linux build tree make C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' If you fix the issue, kindly add following tag as appropriate Reported-by: kbuild test robot <lkp(a)intel.com&gt; sparse warnings: (new ones prefixed by >>) vim +162 drivers/vfio/pci/vfio_pci_rdwr.c 155 156 void __iomem *vfio_pci_get_barmap(void *device_data, int bar) 157 { 158 int ret; 159 struct vfio_pci_device *vdev = device_data; 160 161 ret = vfio_pci_setup_barmap(vdev, bar); 163 } 164 EXPORT_SYMBOL_GPL(vfio_pci_get_barmap); 165 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org