From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jgunthorpe:vfio_iommufd 28/29] drivers/vfio/vfio_main.c:618:6: warning: no previous prototype for 'vfio_assert_device_open'
Date: Thu, 25 Aug 2022 01:16:40 +0800 [thread overview]
Message-ID: <202208250108.KV0cgfXO-lkp@intel.com> (raw)
tree: https://github.com/jgunthorpe/linux vfio_iommufd
head: d2ab4343c9f524e9404059830828188b0f8a15b6
commit: 5016830b7f1d1bf8af24d4ee80fc07a68d835af4 [28/29] vfio: Make vfio_container optionally compiled
config: sparc64-randconfig-r014-20220824 (https://download.01.org/0day-ci/archive/20220825/202208250108.KV0cgfXO-lkp@intel.com/config)
compiler: sparc64-linux-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/jgunthorpe/linux/commit/5016830b7f1d1bf8af24d4ee80fc07a68d835af4
git remote add jgunthorpe https://github.com/jgunthorpe/linux
git fetch --no-tags jgunthorpe vfio_iommufd
git checkout 5016830b7f1d1bf8af24d4ee80fc07a68d835af4
# 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=sparc64 SHELL=/bin/bash drivers/vfio/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/vfio/vfio_main.c:618:6: warning: no previous prototype for 'vfio_assert_device_open' [-Wmissing-prototypes]
618 | bool vfio_assert_device_open(struct vfio_device *device)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/vfio_assert_device_open +618 drivers/vfio/vfio_main.c
cba3345cc494ad drivers/vfio/vfio.c Alex Williamson 2012-07-31 616
eadd86f835c637 drivers/vfio/vfio.c Jason Gunthorpe 2022-05-11 617 /* true if the vfio_device has open_device() called but not close_device() */
79d394f0b0cd09 drivers/vfio/vfio_main.c Jason Gunthorpe 2022-02-18 @618 bool vfio_assert_device_open(struct vfio_device *device)
eadd86f835c637 drivers/vfio/vfio.c Jason Gunthorpe 2022-05-11 619 {
eadd86f835c637 drivers/vfio/vfio.c Jason Gunthorpe 2022-05-11 620 return !WARN_ON_ONCE(!READ_ONCE(device->open_count));
eadd86f835c637 drivers/vfio/vfio.c Jason Gunthorpe 2022-05-11 621 }
eadd86f835c637 drivers/vfio/vfio.c Jason Gunthorpe 2022-05-11 622
:::::: The code at line 618 was first introduced by commit
:::::: 79d394f0b0cd096e2eadbcc0e84b9035efa529c8 vfio: Move container code into vfio_container.c
:::::: TO: Jason Gunthorpe <jgg@nvidia.com>
:::::: CC: Jason Gunthorpe <jgg@nvidia.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-24 17:18 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=202208250108.KV0cgfXO-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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