From: Christian Brauner <brauner@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/hfsplus: wrapper.c: fix kernel-doc warnings
Date: Fri, 8 Dec 2023 14:15:21 +0100 [thread overview]
Message-ID: <20231208-lassen-vorenthalten-eef9da43f947@brauner> (raw)
In-Reply-To: <20231206024317.31020-1-rdunlap@infradead.org>
On Tue, 05 Dec 2023 18:43:17 -0800, Randy Dunlap wrote:
> Fix kernel-doc warnings found when using "W=1".
>
> wrapper.c:48: warning: No description found for return value of 'hfsplus_submit_bio'
> wrapper.c:49: warning: Function parameter or member 'opf' not described in 'hfsplus_submit_bio'
> wrapper.c:49: warning: Excess function parameter 'op' description in 'hfsplus_submit_bio'
> wrapper.c:49: warning: Excess function parameter 'op_flags' description in 'hfsplus_submit_bio'
>
> [...]
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] fs/hfsplus: wrapper.c: fix kernel-doc warnings
https://git.kernel.org/vfs/vfs/c/bff713c4a439
next prev parent reply other threads:[~2023-12-08 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 2:43 [PATCH] fs/hfsplus: wrapper.c: fix kernel-doc warnings Randy Dunlap
2023-12-08 13:15 ` Christian Brauner [this message]
2024-02-09 21:57 ` Bart Van Assche
2024-02-10 4:59 ` Randy Dunlap
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=20231208-lassen-vorenthalten-eef9da43f947@brauner \
--to=brauner@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdunlap@infradead.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).