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/vfio_device_cdev_v7_candidate 24/32] drivers/vfio/group.c:190:5: warning: no previous prototype for 'vfio_device_group_attach_compat_ioas'
Date: Mon, 13 Mar 2023 13:38:11 +0800 [thread overview]
Message-ID: <202303131339.59A950mL-lkp@intel.com> (raw)
tree: https://github.com/yiliu1765/iommufd.git wip/vfio_device_cdev_v7_candidate
head: e3cf0848eac9960f7ecb898d997a9e8200d552b0
commit: 61736068803cb2135b42cbf5618c3f116500aa1d [24/32] vfio-iommufd: Move the bind_iommufd and compat_ioas attach to group.c
config: arc-randconfig-r043-20230313 (https://download.01.org/0day-ci/archive/20230313/202303131339.59A950mL-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 12.1.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/yiliu1765/iommufd/commit/61736068803cb2135b42cbf5618c3f116500aa1d
git remote add yiliu1765-iommufd https://github.com/yiliu1765/iommufd.git
git fetch --no-tags yiliu1765-iommufd wip/vfio_device_cdev_v7_candidate
git checkout 61736068803cb2135b42cbf5618c3f116500aa1d
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash drivers/vfio/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303131339.59A950mL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/vfio/group.c:190:5: warning: no previous prototype for 'vfio_device_group_attach_compat_ioas' [-Wmissing-prototypes]
190 | int vfio_device_group_attach_compat_ioas(struct vfio_device *device,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/vfio_device_group_attach_compat_ioas +190 drivers/vfio/group.c
189
> 190 int vfio_device_group_attach_compat_ioas(struct vfio_device *device,
191 struct iommufd_ctx *iommufd)
192 {
193 u32 ioas_id;
194 int ret;
195
196 lockdep_assert_held(&device->dev_set->lock);
197
198 ret = iommufd_vfio_compat_ioas_get_id(iommufd, &ioas_id);
199 if (ret)
200 return ret;
201
202 /* The legacy path has no way to return the selected pt_id */
203 return device->ops->attach_ioas(device, &ioas_id);
204 }
205
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-13 5:38 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=202303131339.59A950mL-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.