All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/5] vfio: Do not open code the group list search in vfio_create_group()
Date: Sat, 02 Oct 2021 11:19:38 +0800	[thread overview]
Message-ID: <202110021118.eGQuN32h-lkp@intel.com> (raw)
In-Reply-To: <2-v1-fba989159158+2f9b-vfio_group_cdev_jgg@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 5423 bytes --]

Hi Jason,

I love your patch! Perhaps something to improve:

[auto build test WARNING on d9a0cd510c3383b61db6f70a84e0c3487f836a63]

url:    https://github.com/0day-ci/linux/commits/Jason-Gunthorpe/Update-vfio_group-to-use-the-modern-cdev-lifecycle/20211002-072315
base:   d9a0cd510c3383b61db6f70a84e0c3487f836a63
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-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/0day-ci/linux/commit/863433fdbdd6ce5de9dcd683278f3bbfa34b1d0c
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Jason-Gunthorpe/Update-vfio_group-to-use-the-modern-cdev-lifecycle/20211002-072315
        git checkout 863433fdbdd6ce5de9dcd683278f3bbfa34b1d0c
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash drivers/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   drivers/vfio/vfio.c:236: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * IOMMU driver registration
   drivers/vfio/vfio.c:288: warning: Function parameter or member 'group' not described in 'vfio_alloc_group_minor'
   drivers/vfio/vfio.c:288: warning: expecting prototype for Group minor allocation/free(). Prototype was for vfio_alloc_group_minor() instead
   drivers/vfio/vfio.c:308: warning: Function parameter or member 'container' not described in 'vfio_container_get'
   drivers/vfio/vfio.c:308: warning: expecting prototype for Container objects(). Prototype was for vfio_container_get() instead
   drivers/vfio/vfio.c:349: warning: Function parameter or member 'iommu_group' not described in '__vfio_group_get_from_iommu'
>> drivers/vfio/vfio.c:349: warning: expecting prototype for Group objects(). Prototype was for __vfio_group_get_from_iommu() instead
   drivers/vfio/vfio.c:502: warning: Function parameter or member 'device' not described in 'vfio_device_put'
   drivers/vfio/vfio.c:502: warning: expecting prototype for Device objects(). Prototype was for vfio_device_put() instead
   drivers/vfio/vfio.c:605: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Async device support
   drivers/vfio/vfio.c:699: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * VFIO driver API
   drivers/vfio/vfio.c:848: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Get a reference to the vfio_device for a device.  Even if the
   drivers/vfio/vfio.c:982: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * VFIO base fd, /dev/vfio/vfio
   drivers/vfio/vfio.c:1200: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * VFIO Group fd, /dev/vfio/$GROUP
   drivers/vfio/vfio.c:1552: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * VFIO Device fd
   drivers/vfio/vfio.c:1627: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * External user API, exported by symbols to be linked dynamically.
   drivers/vfio/vfio.c:1672: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * External user API, exported by symbols to be linked dynamically.
   drivers/vfio/vfio.c:1751: warning: Function parameter or member 'caps' not described in 'vfio_info_cap_add'
   drivers/vfio/vfio.c:1751: warning: Function parameter or member 'size' not described in 'vfio_info_cap_add'
   drivers/vfio/vfio.c:1751: warning: Function parameter or member 'id' not described in 'vfio_info_cap_add'
   drivers/vfio/vfio.c:1751: warning: Function parameter or member 'version' not described in 'vfio_info_cap_add'
   drivers/vfio/vfio.c:1751: warning: expecting prototype for Sub(). Prototype was for vfio_info_cap_add() instead
   drivers/vfio/vfio.c:2285: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Module/class support


vim +349 drivers/vfio/vfio.c

   343	
   344	/**
   345	 * Group objects - create, release, get, put, search
   346	 */
   347	static struct vfio_group *
   348	__vfio_group_get_from_iommu(struct iommu_group *iommu_group)
 > 349	{
   350		struct vfio_group *group;
   351	
   352		list_for_each_entry(group, &vfio.group_list, vfio_next) {
   353			if (group->iommu_group == iommu_group) {
   354				vfio_group_get(group);
   355				return group;
   356			}
   357		}
   358		return NULL;
   359	}
   360	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 74076 bytes --]

  reply	other threads:[~2021-10-02  3:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 23:22 [PATCH 0/5] Update vfio_group to use the modern cdev lifecycle Jason Gunthorpe
2021-10-01 23:22 ` [PATCH 1/5] vfio: Delete vfio_get/put_group from vfio_iommu_group_notifier() Jason Gunthorpe
2021-10-04 22:25   ` Alex Williamson
2021-10-04 22:34     ` Jason Gunthorpe
2021-10-05  4:01       ` Alex Williamson
2021-10-05 16:17         ` Jason Gunthorpe
2021-10-12  6:32   ` Tian, Kevin
2021-10-12  8:51   ` Liu, Yi L
2021-10-01 23:22 ` [PATCH 2/5] vfio: Do not open code the group list search in vfio_create_group() Jason Gunthorpe
2021-10-02  3:19   ` kernel test robot [this message]
2021-10-12  6:37   ` Tian, Kevin
2021-10-12  8:52   ` Liu, Yi L
2021-10-01 23:22 ` [PATCH 3/5] vfio: Don't leak a group reference if the group already exists Jason Gunthorpe
2021-10-04 22:25   ` Alex Williamson
2021-10-04 22:36     ` Jason Gunthorpe
2021-10-05  4:01       ` Alex Williamson
2021-10-05 14:45         ` Jason Gunthorpe
2021-10-01 23:22 ` [PATCH 4/5] vfio: Use a refcount_t instead of a kref in the vfio_group Jason Gunthorpe
2021-10-04 22:25   ` Alex Williamson
2021-10-04 22:39     ` Jason Gunthorpe
2021-10-12  7:08   ` Tian, Kevin
2021-10-12  9:04   ` Liu, Yi L
2021-10-01 23:22 ` [PATCH 5/5] vfio: Use cdev_device_add() instead of device_create() Jason Gunthorpe
2021-10-12  8:33   ` Tian, Kevin
2021-10-12 12:05     ` Jason Gunthorpe
2021-10-13  1:07       ` Tian, Kevin
2021-10-12  8:57   ` Liu, Yi L
2021-10-13 12:49     ` Jason Gunthorpe
2021-10-13 14:15       ` Liu, Yi L

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=202110021118.eGQuN32h-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.