linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Diana Craciun <diana.craciun@oss.nxp.com>,
	alex.williamson@redhat.com, kvm@vger.kernel.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	laurentiu.tudor@nxp.com, bharatb.linux@gmail.com,
	Diana Craciun <diana.craciun@oss.nxp.com>,
	Bharat Bhushan <Bharat.Bhushan@nxp.com>
Subject: Re: [PATCH v2 8/9] vfio/fsl-mc: trigger an interrupt via eventfd
Date: Sat, 9 May 2020 07:50:41 +0800	[thread overview]
Message-ID: <202005090706.01kG3QUB%lkp@intel.com> (raw)
In-Reply-To: <20200508072039.18146-9-diana.craciun@oss.nxp.com>

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

Hi Diana,

I love your patch! Yet something to improve:

[auto build test ERROR on vfio/next]
[also build test ERROR on linus/master v5.7-rc4 next-20200508]
[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/Diana-Craciun/vfio-fsl-mc-VFIO-support-for-FSL-MC-devices/20200509-034845
base:   https://github.com/awilliam/linux-vfio.git next
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

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

All errors (new ones prefixed by >>):

   drivers/vfio/fsl-mc/vfio_fsl_mc.c: In function 'vfio_fsl_mc_release':
>> drivers/vfio/fsl-mc/vfio_fsl_mc.c:164:9: error: implicit declaration of function 'dprc_reset_container'; did you mean 'resource_contains'? [-Werror=implicit-function-declaration]
      ret = dprc_reset_container(mc_cont->mc_io, 0,
            ^~~~~~~~~~~~~~~~~~~~
            resource_contains
>> drivers/vfio/fsl-mc/vfio_fsl_mc.c:167:6: error: 'DPRC_RESET_OPTION_NON_RECURSIVE' undeclared (first use in this function)
         DPRC_RESET_OPTION_NON_RECURSIVE);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:167:6: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/vfio/fsl-mc/vfio_fsl_mc.c:171:3: error: implicit declaration of function 'fsl_mc_cleanup_irq_pool'; did you mean 'fsl_mc_free_irqs'? [-Werror=implicit-function-declaration]
      fsl_mc_cleanup_irq_pool(mc_cont);
      ^~~~~~~~~~~~~~~~~~~~~~~
      fsl_mc_free_irqs
   drivers/vfio/fsl-mc/vfio_fsl_mc.c: In function 'vfio_fsl_mc_bus_notifier':
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:399:9: error: 'struct fsl_mc_device' has no member named 'driver_override'
      mc_dev->driver_override = kasprintf(GFP_KERNEL, "%s",
            ^~
   drivers/vfio/fsl-mc/vfio_fsl_mc.c: In function 'vfio_fsl_mc_init_device':
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:437:8: error: implicit declaration of function 'dprc_setup'; did you mean 'x2apic_setup'? [-Werror=implicit-function-declaration]
     ret = dprc_setup(mc_dev);
           ^~~~~~~~~~
           x2apic_setup
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:444:8: error: implicit declaration of function 'dprc_scan_container'; did you mean 'init_section_contains'? [-Werror=implicit-function-declaration]
     ret = dprc_scan_container(mc_dev, false);
           ^~~~~~~~~~~~~~~~~~~
           init_section_contains
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:448:3: error: implicit declaration of function 'dprc_cleanup'; did you mean 'pud_clear'? [-Werror=implicit-function-declaration]
      dprc_cleanup(mc_dev);
      ^~~~~~~~~~~~
      pud_clear
   drivers/vfio/fsl-mc/vfio_fsl_mc.c: In function 'vfio_fsl_mc_device_remove':
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:507:14: error: 'struct fsl_mc_device' has no member named 'driver_override'
     kfree(mc_dev->driver_override);
                 ^~
   drivers/vfio/fsl-mc/vfio_fsl_mc.c:508:8: error: 'struct fsl_mc_device' has no member named 'driver_override'
     mc_dev->driver_override = NULL;
           ^~
   cc1: some warnings being treated as errors
--
   drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c: In function 'vfio_fsl_mc_set_irq_trigger':
>> drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c:137:8: error: implicit declaration of function 'fsl_mc_populate_irq_pool'; did you mean 'fsl_mc_allocate_irqs'? [-Werror=implicit-function-declaration]
     ret = fsl_mc_populate_irq_pool(mc_cont,
           ^~~~~~~~~~~~~~~~~~~~~~~~
           fsl_mc_allocate_irqs
>> drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c:138:4: error: 'FSL_MC_IRQ_POOL_MAX_TOTAL_IRQS' undeclared (first use in this function); did you mean 'FSL_MC_NUM_POOL_TYPES'?
       FSL_MC_IRQ_POOL_MAX_TOTAL_IRQS);
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       FSL_MC_NUM_POOL_TYPES
   drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c:138:4: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors

vim +164 drivers/vfio/fsl-mc/vfio_fsl_mc.c

   148	
   149	static void vfio_fsl_mc_release(void *device_data)
   150	{
   151		struct vfio_fsl_mc_device *vdev = device_data;
   152		int ret;
   153	
   154		mutex_lock(&vdev->reflck->lock);
   155	
   156		if (!(--vdev->refcnt)) {
   157			struct fsl_mc_device *mc_dev = vdev->mc_dev;
   158			struct device *cont_dev = fsl_mc_cont_dev(&mc_dev->dev);
   159			struct fsl_mc_device *mc_cont = to_fsl_mc_device(cont_dev);
   160	
   161			vfio_fsl_mc_regions_cleanup(vdev);
   162	
   163			/* reset the device before cleaning up the interrupts */
 > 164			ret = dprc_reset_container(mc_cont->mc_io, 0,
   165			      mc_cont->mc_handle,
   166				  mc_cont->obj_desc.id,
 > 167				  DPRC_RESET_OPTION_NON_RECURSIVE);
   168	
   169			vfio_fsl_mc_irqs_cleanup(vdev);
   170	
 > 171			fsl_mc_cleanup_irq_pool(mc_cont);
   172		}
   173	
   174		mutex_unlock(&vdev->reflck->lock);
   175	
   176		module_put(THIS_MODULE);
   177	}
   178	

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

  reply	other threads:[~2020-05-08 23:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  7:20 [PATCH v2 0/9] vfio/fsl-mc: VFIO support for FSL-MC devices Diana Craciun
2020-05-08  7:20 ` [PATCH v2 1/9] vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devices Diana Craciun
2020-05-08  7:20 ` [PATCH v2 2/9] vfio/fsl-mc: Scan DPRC objects on vfio-fsl-mc driver bind Diana Craciun
2020-05-08 22:49   ` kbuild test robot
2020-06-02  4:12   ` Alex Williamson
2020-05-08  7:20 ` [PATCH v2 3/9] vfio/fsl-mc: Implement VFIO_DEVICE_GET_INFO ioctl Diana Craciun
2020-05-08  7:20 ` [PATCH v2 4/9] vfio/fsl-mc: Implement VFIO_DEVICE_GET_REGION_INFO ioctl call Diana Craciun
2020-06-02  4:12   ` Alex Williamson
2020-06-04 18:37     ` Diana Craciun OSS
2020-05-08  7:20 ` [PATCH v2 5/9] vfio/fsl-mc: Allow userspace to MMAP fsl-mc device MMIO regions Diana Craciun
2020-06-02  4:12   ` Alex Williamson
2020-06-04 18:41     ` Diana Craciun OSS
2020-05-08  7:20 ` [PATCH v2 6/9] vfio/fsl-mc: Added lock support in preparation for interrupt handling Diana Craciun
2020-05-08  7:20 ` [PATCH v2 7/9] vfio/fsl-mc: Add irq infrastructure for fsl-mc devices Diana Craciun
2020-05-08  7:20 ` [PATCH v2 8/9] vfio/fsl-mc: trigger an interrupt via eventfd Diana Craciun
2020-05-08 23:50   ` kbuild test robot [this message]
2020-05-08  7:20 ` [PATCH v2 9/9] vfio/fsl-mc: Add read/write support for fsl-mc devices Diana Craciun
2020-05-09  0:47   ` kbuild test robot

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=202005090706.01kG3QUB%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Bharat.Bhushan@nxp.com \
    --cc=alex.williamson@redhat.com \
    --cc=bharatb.linux@gmail.com \
    --cc=diana.craciun@oss.nxp.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvm@vger.kernel.org \
    --cc=laurentiu.tudor@nxp.com \
    --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;
as well as URLs for NNTP newsgroup(s).