From: Greg KH <gregkh@linuxfoundation.org>
To: Arshad Hussain <arshad.super@gmail.com>
Cc: linux-erofs@lists.ozlabs.org, gaoxiang25@huawei.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
yuchao0@huawei.com
Subject: Re: [PATCH] [PATCH 1/1] staging: erofs: Add function comment for erofs/super.c
Date: Sun, 17 Mar 2019 12:11:12 +0100 [thread overview]
Message-ID: <20190317111112.GA4614@kroah.com> (raw)
In-Reply-To: <20190312210640.2175-1-arshad.super@gmail.com>
On Wed, Mar 13, 2019 at 02:36:40AM +0530, Arshad Hussain wrote:
> This patch adds functions comment for file erofs/super.c in
> sphinx format.
>
> Signed-off-by: Arshad Hussain <arshad.super@gmail.com>
> ---
> drivers/staging/erofs/super.c | 135 ++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 131 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/erofs/super.c b/drivers/staging/erofs/super.c
> index 15c784fba879..60bfc3e8db7a 100644
> --- a/drivers/staging/erofs/super.c
> +++ b/drivers/staging/erofs/super.c
> @@ -30,6 +30,11 @@ static void init_once(void *ptr)
> inode_init_once(&vi->vfs_inode);
> }
>
> +/**
> + * erofs_init_inode_cache(): Create & initialize inode cache
> + *
> + * Returns: 0 on Success. Errno Otherwise.
> + */
> static int __init erofs_init_inode_cache(void)
Why do you need kernel doc comments for local functions? That should
not be needed. No tool is going through this file to create
documentation, right? And documentation is only needed for functions
that are called outside of the file at most, and usually only needed for
functions that other drivers/subsystems can call.
And for a function name like this, it is pretty obvious what it does, no
comment should be needed at all.
Same for the other changes here, I do not think it is needed at all.
thanks,
greg k-h
prev parent reply other threads:[~2019-03-17 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:06 [PATCH] [PATCH 1/1] staging: erofs: Add function comment for erofs/super.c Arshad Hussain
2019-03-13 6:53 ` Gao Xiang
2019-03-16 6:18 ` arshad hussain
2019-03-17 11:11 ` Greg KH [this message]
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=20190317111112.GA4614@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arshad.super@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gaoxiang25@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.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