From: Randy Dunlap <rdunlap@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>,
paul@paul-moore.com, stephen.smalley.work@gmail.com,
eparis@parisplace.org
Cc: selinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selinux: Corrected comment to match kernel-doc comment
Date: Sat, 24 Apr 2021 08:46:22 -0700 [thread overview]
Message-ID: <9428b8d9-976a-cfcb-0a97-01a18b92140a@infradead.org> (raw)
In-Reply-To: <1619263085-5047-1-git-send-email-jrdr.linux@gmail.com>
On 4/24/21 4:18 AM, Souptick Joarder wrote:
> Kernel test robot throws below warning ->
>
> security/selinux/avc.c:822: warning: This comment starts with '/**', but
> isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>
> Updated the comment to align with kernel-doc comment.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> ---
> security/selinux/avc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/selinux/avc.c b/security/selinux/avc.c
> index ad451cf..04a886b 100644
> --- a/security/selinux/avc.c
> +++ b/security/selinux/avc.c
> @@ -818,7 +818,7 @@ int __init avc_add_callback(int (*callback)(u32 event), u32 events)
> return rc;
> }
>
> -/**
> +/*
> * avc_update_node Update an AVC entry
or
* avc_update_node - Update an AVC entry
would work also. :)
And leave the /**.
Mostly we want to have kernel-doc for exported (non-static) functions,
but this file doesn't exactly conform to that, so the latter fix
is more preferable IMO.
> * @event : Updating event
> * @perms : Permission mask bits
>
--
~Randy
prev parent reply other threads:[~2021-04-24 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 11:18 Souptick Joarder
2021-04-24 15:46 ` Randy Dunlap [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=9428b8d9-976a-cfcb-0a97-01a18b92140a@infradead.org \
--to=rdunlap@infradead.org \
--cc=eparis@parisplace.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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®