From: Gary R Hook <gary.hook@amd.com>
To: Greg KH <greg@kroah.com>
Cc: iommu@lists.linux-foundation.org, joro@8bytes.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/2] iommu - Enable debugfs exposure of IOMMU driver internals
Date: Tue, 12 Jun 2018 13:39:04 -0500 [thread overview]
Message-ID: <bfee19e5-7953-7bda-2c46-9dbb4d002512@amd.com> (raw)
In-Reply-To: <20180605170824.GA11965@kroah.com>
On 06/05/2018 12:08 PM, Greg KH wrote:
> On Tue, Jun 05, 2018 at 12:01:41PM -0500, Gary R Hook wrote:
>>>> +/**
>>>> + * iommu_debugfs_new_driver_dir - create a vendor directory under debugfs/iommu
>>>> + * @vendor: name of the vendor-specific subdirectory to create
>>>> + *
>>>> + * This function is called by an IOMMU driver to create the top-level debugfs
>>>> + * directory for that driver.
>>>> + *
>>>> + * Return: upon success, a pointer to the dentry for the new directory.
>>>> + * NULL in case of failure.
>>>> + */
>>>> +struct dentry *iommu_debugfs_new_driver_dir(const char *vendor)
>>>> +{
>>>> + struct dentry *d_new;
>>>> +
>>>> + d_new = debugfs_create_dir(vendor, iommu_debugfs_dir);
>>>> +
>>>> + return d_new;
>>>> +}
>>>> +EXPORT_SYMBOL_GPL(iommu_debugfs_new_driver_dir);
>>>
>>> Why are you wrapping a debugfs call? Why not just export
>>> iommu_debugfs_dir instead?
>>
>> It was a choice, as I stated in my other post. It is not a requirement.
>> If you resolutely reject this approach, that's fine. I'll change it, no
>> worries.
>
> Either is fine, but if it stays, it should stay a single line function
> :)
>
> thanks,
>
> greg k-h
>
Then I shall leave it as a black-box function. Single line, of course.
Thank you.
next prev parent reply other threads:[~2018-06-12 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 18:23 [PATCH v8 0/2] Base enablement of IOMMU debugfs support Gary R Hook
2018-05-29 18:23 ` [PATCH v8 1/2] iommu - Enable debugfs exposure of IOMMU driver internals Gary R Hook
2018-05-29 18:41 ` Greg KH
2018-06-05 17:01 ` Gary R Hook
2018-06-05 17:08 ` Greg KH
2018-06-12 18:39 ` Gary R Hook [this message]
2018-05-29 18:23 ` [PATCH v8 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU Gary R Hook
2018-05-29 18:39 ` Greg KH
2018-06-05 1:23 ` Randy Dunlap
2018-06-12 18:40 ` Gary R Hook
2018-06-05 16:58 ` Gary R Hook
2018-06-05 17:06 ` Greg KH
2018-06-12 18:37 ` 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=bfee19e5-7953-7bda-2c46-9dbb4d002512@amd.com \
--to=gary.hook@amd.com \
--cc=greg@kroah.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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;
as well as URLs for NNTP newsgroup(s).