public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Serge Hallyn <sergeh@kernel.org>,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] cred: cred.h: fix kernel-doc warnings
Date: Mon, 02 Mar 2026 17:08:02 -0500	[thread overview]
Message-ID: <0b3c6d530122d72a1047db17d016cf05@paul-moore.com> (raw)
In-Reply-To: <20260302005154.3468238-1-rdunlap@infradead.org>

On Mar  1, 2026 Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> Use the correct function parameter names, function names, or kernel-doc
> format, and add function return comment sections to avoid kernel-doc
> warnings:
> 
> Warning: include/linux/cred.h:43 function parameter 'gi' not described
>  in 'get_group_info'
> Warning: include/linux/cred.h:43 No description found for return value
>  of 'get_group_info'
> Warning: include/linux/cred.h:213 No description found for return value
>  of 'get_cred_many'
> Warning: include/linux/cred.h:260 function parameter '_cred' not described
>  in 'put_cred_many'
> Warning: include/linux/cred.h:260 expecting prototype for put_cred().
>  Prototype was for put_cred_many() instead
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Paul Moore <paul@paul-moore.com>
> Cc: Serge Hallyn <sergeh@kernel.org>
> Cc: linux-security-module@vger.kernel.org
> 
>  include/linux/cred.h |   10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)

Merged into lsm/dev, thanks.

--
paul-moore.com

      reply	other threads:[~2026-03-02 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  0:51 [PATCH] cred: cred.h: fix kernel-doc warnings Randy Dunlap
2026-03-02 22:08 ` Paul Moore [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=0b3c6d530122d72a1047db17d016cf05@paul-moore.com \
    --to=paul@paul-moore.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sergeh@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