From: Christian Brauner <brauner@kernel.org>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Christian Brauner <brauner@kernel.org>,
Anton Altaparmakov <anton@tuxera.com>,
Namjae Jeon <linkinjeon@kernel.org>,
linux-ntfs-dev@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ntfs: dir.c: fix kernel-doc function parameter warnings
Date: Tue, 19 Dec 2023 14:07:08 +0100 [thread overview]
Message-ID: <20231219-lockruf-passt-c4ac862c57cb@brauner> (raw)
In-Reply-To: <20231219045414.24670-1-rdunlap@infradead.org>
On Mon, 18 Dec 2023 20:54:14 -0800, Randy Dunlap wrote:
> Correct the kernel-doc function parameter warnings for function
> ntfs_dir_fsync() to prevent the following kernel-doc warnings:
>
> dir.c:1489: warning: Function parameter or member 'start' not described in 'ntfs_dir_fsync'
> dir.c:1489: warning: Function parameter or member 'end' not described in 'ntfs_dir_fsync'
> dir.c:1489: warning: Excess function parameter 'dentry' description in 'ntfs_dir_fsync'
>
> [...]
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.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] ntfs: dir.c: fix kernel-doc function parameter warnings
https://git.kernel.org/vfs/vfs/c/be4887a964e2
prev parent reply other threads:[~2023-12-19 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 4:54 [PATCH] ntfs: dir.c: fix kernel-doc function parameter warnings Randy Dunlap
2023-12-19 7:45 ` Namjae Jeon
2023-12-19 13:07 ` 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=20231219-lockruf-passt-c4ac862c57cb@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anton@tuxera.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=rdunlap@infradead.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