From: Christian Brauner <brauner@kernel.org>
To: Anuradha Weeraman <anuradha@debian.org>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/open.c: Fix W=1 kernel doc warnings
Date: Mon, 15 May 2023 12:41:11 +0200 [thread overview]
Message-ID: <20230515-ritzen-abpfiff-4782ae08368e@brauner> (raw)
In-Reply-To: <20230506182928.384105-1-anuradha@debian.org>
On Sat, 06 May 2023 23:59:27 +0530, Anuradha Weeraman wrote:
> fs/open.c: In functions 'setattr_vfsuid' and 'setattr_vfsgid':
> warning: Function parameter or member 'attr' not described
> - Fix warning by removing kernel-doc for these as they are static
> inline functions and not required to be exposed via kernel-doc.
>
> fs/open.c:
> warning: Excess function parameter 'opened' description in 'finish_open'
> warning: Excess function parameter 'cred' description in 'vfs_open'
> - Fix by removing the parameters from the kernel-doc as they are no
> longer required by the function.
>
> [...]
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] fs/open.c: Fix W=1 kernel doc warnings
https://git.kernel.org/vfs/vfs/c/1c4f10518c3a
prev parent reply other threads:[~2023-05-15 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 18:29 [PATCH] fs/open.c: Fix W=1 kernel doc warnings Anuradha Weeraman
2023-05-15 10:41 ` Christian Brauner [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=20230515-ritzen-abpfiff-4782ae08368e@brauner \
--to=brauner@kernel.org \
--cc=anuradha@debian.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).