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 v11 11/12] vduse: Introduce VDUSE - vDPA Device in Userspace
Date: Thu, 19 Aug 2021 11:09:15 +0800	[thread overview]
Message-ID: <202108191121.ILenalns-lkp@intel.com> (raw)
In-Reply-To: <20210818120642.165-12-xieyongji@bytedance.com>

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

Hi Xie,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on vhost/linux-next]
[also build test ERROR on linus/master next-20210818]
[cannot apply to iommu/next lwn/docs-next v5.14-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Xie-Yongji/Introduce-VDUSE-vDPA-Device-in-Userspace/20210818-201209
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/0b6102bc9db2d526393eaf9e5b8412940445a34b
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Xie-Yongji/Introduce-VDUSE-vDPA-Device-in-Userspace/20210818-201209
        git checkout 0b6102bc9db2d526393eaf9e5b8412940445a34b
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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

All errors (new ones prefixed by >>):

>> drivers/vdpa/vdpa_user/vduse_dev.c:698:21: error: initialization of 'u16 (*)(struct vdpa_device *)' {aka 'short unsigned int (*)(struct vdpa_device *)'} from incompatible pointer type 'u16 (*)(struct vdpa_device *, u16)' {aka 'short unsigned int (*)(struct vdpa_device *, short unsigned int)'} [-Werror=incompatible-pointer-types]
     698 |  .get_vq_num_max  = vduse_vdpa_get_vq_num_max,
         |                     ^~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/vdpa/vdpa_user/vduse_dev.c:698:21: note: (near initialization for 'vduse_vdpa_config_ops.get_vq_num_max')
   cc1: some warnings being treated as errors


vim +698 drivers/vdpa/vdpa_user/vduse_dev.c

   684	
   685	static const struct vdpa_config_ops vduse_vdpa_config_ops = {
   686		.set_vq_address		= vduse_vdpa_set_vq_address,
   687		.kick_vq		= vduse_vdpa_kick_vq,
   688		.set_vq_cb		= vduse_vdpa_set_vq_cb,
   689		.set_vq_num             = vduse_vdpa_set_vq_num,
   690		.set_vq_ready		= vduse_vdpa_set_vq_ready,
   691		.get_vq_ready		= vduse_vdpa_get_vq_ready,
   692		.set_vq_state		= vduse_vdpa_set_vq_state,
   693		.get_vq_state		= vduse_vdpa_get_vq_state,
   694		.get_vq_align		= vduse_vdpa_get_vq_align,
   695		.get_features		= vduse_vdpa_get_features,
   696		.set_features		= vduse_vdpa_set_features,
   697		.set_config_cb		= vduse_vdpa_set_config_cb,
 > 698		.get_vq_num_max		= vduse_vdpa_get_vq_num_max,
   699		.get_device_id		= vduse_vdpa_get_device_id,
   700		.get_vendor_id		= vduse_vdpa_get_vendor_id,
   701		.get_status		= vduse_vdpa_get_status,
   702		.set_status		= vduse_vdpa_set_status,
   703		.get_config_size	= vduse_vdpa_get_config_size,
   704		.get_config		= vduse_vdpa_get_config,
   705		.set_config		= vduse_vdpa_set_config,
   706		.get_generation		= vduse_vdpa_get_generation,
   707		.reset			= vduse_vdpa_reset,
   708		.set_map		= vduse_vdpa_set_map,
   709		.free			= vduse_vdpa_free,
   710	};
   711	

---
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: 65146 bytes --]

  reply	other threads:[~2021-08-19  3:09 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 12:06 [PATCH v11 00/12] Introduce VDUSE - vDPA Device in Userspace Xie Yongji
2021-08-18 12:06 ` Xie Yongji
2021-08-18 12:06 ` [PATCH v11 01/12] iova: Export alloc_iova_fast() and free_iova_fast() Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-23  6:24   ` Jason Wang
2021-08-23  6:24     ` Jason Wang
2021-08-23  6:24     ` Jason Wang
2021-08-24 18:08   ` Michael S. Tsirkin
2021-08-24 18:08     ` Michael S. Tsirkin
2021-08-24 18:08     ` Michael S. Tsirkin
2021-08-25  9:55     ` Will Deacon
2021-08-25  9:55       ` Will Deacon
2021-08-25  9:55       ` Will Deacon
2021-08-25 10:39       ` John Garry
2021-08-25 10:39         ` John Garry
2021-08-25 12:17         ` Yongji Xie
2021-08-25 12:17           ` Yongji Xie
2021-08-27  9:03           ` John Garry
2021-08-27  9:03             ` John Garry
2021-08-18 12:06 ` [PATCH v11 02/12] file: Export receive_fd() to modules Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-18 12:06 ` [PATCH v11 03/12] vdpa: Fix some coding style issues Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-23  6:27   ` Jason Wang
2021-08-23  6:27     ` Jason Wang
2021-08-23  6:27     ` Jason Wang
2021-08-24 11:09   ` Stefano Garzarella
2021-08-24 11:09     ` Stefano Garzarella
2021-08-24 11:09     ` Stefano Garzarella
2021-08-18 12:06 ` [PATCH v11 04/12] vdpa: Add reset callback in vdpa_config_ops Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-23  6:31   ` Jason Wang
2021-08-23  6:31     ` Jason Wang
2021-08-23  6:31     ` Jason Wang
2021-08-23  7:44     ` Yongji Xie
2021-08-23  7:44       ` Yongji Xie
2021-08-18 12:06 ` [PATCH v11 05/12] vhost-vdpa: Handle the failure of vdpa_reset() Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-23  6:32   ` Jason Wang
2021-08-23  6:32     ` Jason Wang
2021-08-23  6:32     ` Jason Wang
2021-08-24 11:12   ` Stefano Garzarella
2021-08-24 11:12     ` Stefano Garzarella
2021-08-24 11:12     ` Stefano Garzarella
2021-08-18 12:06 ` [PATCH v11 06/12] vhost-iotlb: Add an opaque pointer for vhost IOTLB Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-18 12:06 ` [PATCH v11 07/12] vdpa: Add an opaque pointer for vdpa_config_ops.dma_map() Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-18 12:06 ` [PATCH v11 08/12] vdpa: factor out vhost_vdpa_pa_map() and vhost_vdpa_pa_unmap() Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-18 12:06 ` [PATCH v11 09/12] vdpa: Support transferring virtual addressing during DMA mapping Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-18 12:06 ` [PATCH v11 10/12] vduse: Implement an MMU-based software IOTLB Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-27  8:57   ` John Garry
2021-08-27  8:57     ` John Garry
2021-08-27  9:25     ` Yongji Xie
2021-08-27  9:25       ` Yongji Xie
2021-08-18 12:06 ` [PATCH v11 11/12] vduse: Introduce VDUSE - vDPA Device in Userspace Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-19  3:09   ` kernel test robot [this message]
2021-08-23  6:56   ` Jason Wang
2021-08-23  6:56     ` Jason Wang
2021-08-23  6:56     ` Jason Wang
2021-08-24 18:10   ` Michael S. Tsirkin
2021-08-24 18:10     ` Michael S. Tsirkin
2021-08-24 18:10     ` Michael S. Tsirkin
2021-08-25  5:37     ` Yongji Xie
2021-08-25  5:37       ` Yongji Xie
2021-08-18 12:06 ` [PATCH v11 12/12] Documentation: Add documentation for VDUSE Xie Yongji
2021-08-18 12:06   ` Xie Yongji
2021-08-23  6:57   ` Jason Wang
2021-08-23  6:57     ` Jason Wang
2021-08-23  6:57     ` Jason Wang
2021-08-23  7:54   ` Jason Wang
2021-08-23  7:54     ` Jason Wang
2021-08-23  7:54     ` Jason Wang

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=202108191121.ILenalns-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.