From: Gary R Hook <gary.hook@amd.com>
To: Joe Perches <joe@perches.com>, "Hook, Gary" <ghook@amd.com>,
kbuild test robot <lkp@intel.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 15:07:08 -0500 [thread overview]
Message-ID: <239fdd0c-9497-7275-4e74-d6ccd028e823@amd.com> (raw)
In-Reply-To: <e671945494d54cdcf65c6d2af9f9f69d65fb2583.camel@perches.com>
On 05/08/2018 01:48 PM, Joe Perches wrote:
> On Tue, 2018-05-08 at 12:08 -0500, Hook, Gary wrote:
>> On 5/7/2018 6:47 PM, kbuild test robot wrote:
>>>
>>> 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
>>
>> I have no problems with adding parameter names. But
>> scripts/checkpatch.pl doesn't seem to check for this, nor require it.
>> Should checkpatch be updated?
>
> I'm pretty sure that's not feasible.
Ugh. This is a definition, not a declaration. My bad. Which is likely
why I decided to apologize up front.
> And when the compiler tells you you've stuffed up some
> syntactical bit, why should checkpatch duplicate the
> output error message too?
Well, that's the point: neither the 4.8 nor 5.4 compiler complained
about this. Not as an error, despite the fact that (now that I read what
is actually here, as opposed to what I think is there) this is wrong.
Had an error message been emitted, and the make stopped, I would have
figure this out before embarrassing myself in front of the entire interwebs.
> btw: That's an unnecessary ; at the end of that non-void
> function and it should probably be something like:
You are correct, sir. I've made a change on this.
>
> static inline struct dentry *iommu_debugfs_new_driver_dir(char *dir)
> {
> return NULL;
> }
Thanks for taking a few moments to comment. Much appreciated.
next prev parent reply other threads:[~2018-05-08 20:07 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
2018-05-08 17:08 ` Hook, Gary
2018-05-08 18:48 ` Joe Perches
2018-05-08 20:07 ` Gary R Hook [this message]
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=239fdd0c-9497-7275-4e74-d6ccd028e823@amd.com \
--to=gary.hook@amd.com \
--cc=ghook@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joe@perches.com \
--cc=joro@8bytes.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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®