mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Gary R Hook <gary.hook@amd.com>
Cc: kbuild-all@01.org, iommu@lists.linux-foundation.org,
	joro@8bytes.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] iommu - Enable debugfs exposure of IOMMU driver internals
Date: Tue, 8 May 2018 07:47:44 +0800	[thread overview]
Message-ID: <201805080700.Jm8moLQz%fengguang.wu@intel.com> (raw)
In-Reply-To: <152572332370.3235.16541462864315443906.stgit@sosxen2.amd.com>

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

Hi Gary,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on iommu/next]
[also build test ERROR on v4.17-rc4 next-20180507]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Gary-R-Hook/iommu-Enable-debugfs-exposure-of-IOMMU-driver-internals/20180508-062918
base:   https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
config: x86_64-randconfig-x016-201818 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All error/warnings (new ones prefixed by >>):

   In file included from include/linux/intel-iommu.h:32:0,
                    from drivers/gpu/drm/i915/i915_drv.h:41,
                    from drivers/gpu/drm/i915/i915_oa_bxt.c:31:
   include/linux/iommu.h: In function 'iommu_debugfs_new_driver_dir':
>> include/linux/iommu.h:706:8: error: parameter name omitted
    struct dentry *iommu_debugfs_new_driver_dir(char *) {};
           ^~~~~~
   In file included from include/linux/intel-iommu.h:32:0,
                    from drivers/gpu/drm/i915/i915_drv.h:41,
                    from drivers/gpu/drm/i915/i915_oa_bxt.c:31:
>> include/linux/iommu.h:706:8: warning: control reaches end of non-void function [-Wreturn-type]
    struct dentry *iommu_debugfs_new_driver_dir(char *) {};
           ^~~~~~

vim +706 include/linux/iommu.h

   700	
   701	#ifdef CONFIG_IOMMU_DEBUGFS
   702	void iommu_debugfs_setup(void);
   703	struct dentry *iommu_debugfs_new_driver_dir(char *);
   704	#else
   705	static inline void iommu_debugfs_setup(void) {}
 > 706	struct dentry *iommu_debugfs_new_driver_dir(char *) {};
   707	#endif
   708	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

  reply	other threads:[~2018-05-07 23:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 20:01 [PATCH v5 0/2] Base enablement of IOMMU debugfs support Gary R Hook
2018-05-07 20:02 ` [PATCH v5 1/2] iommu - Enable debugfs exposure of IOMMU driver internals Gary R Hook
2018-05-07 23:47   ` kbuild test robot [this message]
2018-05-08 17:08     ` Hook, Gary
2018-05-08 18:48       ` Joe Perches
2018-05-08 20:07         ` Gary R Hook
2018-05-08 20:42           ` Joe Perches
2018-05-08 20:48             ` Gary R Hook
2018-05-07 20:02 ` [PATCH v5 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU Gary R Hook

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=201805080700.Jm8moLQz%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=gary.hook@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kbuild-all@01.org \
    --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

all inboxes | Powered by JetHome®