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 v2 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU
Date: Fri, 6 Apr 2018 03:57:28 +0800 [thread overview]
Message-ID: <201804060323.y8KXdJrq%fengguang.wu@intel.com> (raw)
In-Reply-To: <152286810663.3286.1200646003836116320.stgit@taos>
[-- Attachment #1: Type: text/plain, Size: 1763 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.16 next-20180405]
[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-the-IOMMU/20180405-151608
base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
config: x86_64-randconfig-s2-04060234 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers//iommu/amd_iommu_debugfs.c: In function 'amd_iommu_debugfs_setup':
>> drivers//iommu/amd_iommu_debugfs.c:31:11: error: implicit declaration of function 'iommu_debugfs_setup' [-Werror=implicit-function-declaration]
d_top = iommu_debugfs_setup();
^~~~~~~~~~~~~~~~~~~
drivers//iommu/amd_iommu_debugfs.c:31:9: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
d_top = iommu_debugfs_setup();
^
cc1: some warnings being treated as errors
vim +/iommu_debugfs_setup +31 drivers//iommu/amd_iommu_debugfs.c
20
21 void amd_iommu_debugfs_setup(struct amd_iommu *iommu)
22 {
23 char name[MAX_NAME_LEN + 1];
24 struct dentry *d_top;
25
26 if (!debugfs_initialized())
27 return;
28
29 mutex_lock(&amd_iommu_debugfs_lock);
30 if (!amd_iommu_debugfs) {
> 31 d_top = iommu_debugfs_setup();
---
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: 28736 bytes --]
next prev parent reply other threads:[~2018-04-05 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 18:54 [PATCH v2 0/2] Base enablement of IOMMU debugfs support Gary R Hook
2018-04-04 18:54 ` [PATCH v2 1/2] iommu - Enable debugfs exposure of the IOMMU Gary R Hook
2018-04-04 18:55 ` [PATCH v2 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU Gary R Hook
2018-04-05 8:12 ` kbuild test robot
2018-04-05 19:57 ` kbuild test robot [this message]
2018-04-05 20:00 ` Tom Lendacky
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=201804060323.y8KXdJrq%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®