linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kbuild-all@lists.01.org, mst@redhat.com,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH V6 8/8] virtio: Intel IFC VF driver for VDPA
Date: Wed, 18 Mar 2020 21:30:48 +0800	[thread overview]
Message-ID: <202003182159.1PHxNmwM%lkp@intel.com> (raw)
In-Reply-To: <20200318080327.21958-9-jasowang@redhat.com>

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

Hi Jason,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on vhost/linux-next]
[also build test ERROR on linux/master linus/master v5.6-rc6 next-20200317]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Jason-Wang/vDPA-support/20200318-191435
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=9.2.0 make.cross ARCH=sh 

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

All errors (new ones prefixed by >>):

   drivers/virtio/vdpa/ifcvf/ifcvf_main.c: In function 'ifcvf_probe':
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:409:30: error: implicit declaration of function 'pci_iomap_range'; did you mean 'pci_unmap_page'? [-Werror=implicit-function-declaration]
     409 |   vf->mem_resource[i].addr = pci_iomap_range(pdev, i, 0,
         |                              ^~~~~~~~~~~~~~~
         |                              pci_unmap_page
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:409:28: warning: assignment to 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
     409 |   vf->mem_resource[i].addr = pci_iomap_range(pdev, i, 0,
         |                            ^
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:443:2: error: implicit declaration of function 'pci_free_irq_vectors'; did you mean 'pci_alloc_irq_vectors'? [-Werror=implicit-function-declaration]
     443 |  pci_free_irq_vectors(pdev);
         |  ^~~~~~~~~~~~~~~~~~~~
         |  pci_alloc_irq_vectors
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c: In function 'ifcvf_remove':
>> drivers/virtio/vdpa/ifcvf/ifcvf_main.c:463:4: error: implicit declaration of function 'pci_iounmap'; did you mean 'pcim_iounmap'? [-Werror=implicit-function-declaration]
     463 |    pci_iounmap(pdev, vf->mem_resource[i].addr);
         |    ^~~~~~~~~~~
         |    pcim_iounmap
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c: At top level:
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:491:1: warning: data definition has no type or storage class
     491 | module_pci_driver(ifcvf_driver);
         | ^~~~~~~~~~~~~~~~~
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:491:1: error: type defaults to 'int' in declaration of 'module_pci_driver' [-Werror=implicit-int]
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:491:1: warning: parameter names (without types) in function declaration
   drivers/virtio/vdpa/ifcvf/ifcvf_main.c:484:26: warning: 'ifcvf_driver' defined but not used [-Wunused-variable]
     484 | static struct pci_driver ifcvf_driver = {
         |                          ^~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +463 drivers/virtio/vdpa/ifcvf/ifcvf_main.c

   452	
   453	static void ifcvf_remove(struct pci_dev *pdev)
   454	{
   455		struct ifcvf_adapter *adapter = pci_get_drvdata(pdev);
   456		struct ifcvf_hw *vf;
   457		int i;
   458	
   459		ifcvf_vdpa_detach(adapter);
   460		vf = &adapter->vf;
   461		for (i = 0; i < IFCVF_PCI_MAX_RESOURCE; i++) {
   462			if (vf->mem_resource[i].addr) {
 > 463				pci_iounmap(pdev, vf->mem_resource[i].addr);
   464				vf->mem_resource[i].addr = NULL;
   465			}
   466		}
   467	
   468		ifcvf_destroy_adapter(adapter);
   469		pci_free_irq_vectors(pdev);
   470		pci_release_regions(pdev);
   471		pci_disable_device(pdev);
   472		kfree(adapter);
   473	}
   474	

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

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

      parent reply	other threads:[~2020-03-18 13:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  8:03 [PATCH V6 0/8] vDPA support Jason Wang
2020-03-18  8:03 ` [PATCH V6 1/8] vhost: allow per device message handler Jason Wang
2020-03-18  8:03 ` [PATCH V6 2/8] vhost: factor out IOTLB Jason Wang
2020-03-18  8:03 ` [PATCH V6 3/8] vringh: IOTLB support Jason Wang
2020-03-18 16:49   ` kbuild test robot
2020-03-18 19:48   ` kbuild test robot
2020-03-18  8:03 ` [PATCH V6 4/8] vDPA: introduce vDPA bus Jason Wang
2020-03-18  8:03 ` [PATCH V6 5/8] virtio: introduce a vDPA based transport Jason Wang
2020-03-18  8:03 ` [PATCH V6 6/8] vhost: introduce vDPA-based backend Jason Wang
2020-03-18  8:03 ` [PATCH V6 7/8] vdpasim: vDPA device simulator Jason Wang
2020-03-18  8:03 ` [PATCH V6 8/8] virtio: Intel IFC VF driver for VDPA Jason Wang
2020-03-18 12:22   ` Jason Gunthorpe
2020-03-19  7:28     ` Zhu Lingshan
2020-03-19  8:14     ` Jason Wang
2020-03-19 13:02       ` Jason Gunthorpe
2020-03-20  9:17         ` Jason Wang
2020-03-18 13:24   ` kbuild test robot
2020-03-18 13:30   ` kbuild test robot [this message]

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=202003182159.1PHxNmwM%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jasowang@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).