From: kernel test robot <lkp@intel.com>
To: aubrey.li@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [anolis-intel-cloud:devel-5.10 1/1] drivers/vfio/mdev/idxd/vdev.c:1058:6: warning: no previous prototype for 'vidxd_free_ims_entries'
Date: Sat, 8 Mar 2025 12:33:10 +0800 [thread overview]
Message-ID: <202503081202.BBujIyUf-lkp@intel.com> (raw)
tree: https://gitee.com/anolis/intel-cloud-kernel.git devel-5.10
head: 797aae63f086cf8250bfbb8395ab310c525ac4a6
commit: 4f35c1745a635e3bb8eee3ebd769d7e5b262d01e [1/1] vfio/mdev: idxd: add basic mdev registration and helper functions
config: x86_64-anolis-intel-cloud-devel-5.10 (https://download.01.org/0day-ci/archive/20250308/202503081202.BBujIyUf-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250308/202503081202.BBujIyUf-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/202503081202.BBujIyUf-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/vfio/mdev/idxd/vdev.c:1058:6: warning: no previous prototype for 'vidxd_free_ims_entries' [-Wmissing-prototypes]
1058 | void vidxd_free_ims_entries(struct vdcm_idxd *vidxd)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/vidxd_free_ims_entries +1058 drivers/vfio/mdev/idxd/vdev.c
1057
> 1058 void vidxd_free_ims_entries(struct vdcm_idxd *vidxd)
1059 {
1060 struct mdev_device *mdev = vidxd->ivdev.mdev;
1061 struct device *dev = mdev_dev(mdev);
1062
1063 msi_domain_free_irqs(dev_get_msi_domain(dev), dev);
1064 }
1065
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-08 4:33 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=202503081202.BBujIyUf-lkp@intel.com \
--to=lkp@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.