From: Chuck Lever <chuck.lever@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: xdr.h: fix all kernel-doc warnings
Date: Tue, 3 Mar 2026 11:37:40 -0500 [thread overview]
Message-ID: <ccfa6bf5-6459-4633-bcbe-dfa487c8057b@oracle.com> (raw)
In-Reply-To: <20260228220922.2982492-1-rdunlap@infradead.org>
On 2/28/26 5:09 PM, Randy Dunlap wrote:
> Correct a function parameter name (s/page/folio/) and add function
> return value sections for multiple functions to eliminate
> kernel-doc warnings:
>
> Warning: include/linux/sunrpc/xdr.h:298 function parameter 'folio' not
> described in 'xdr_set_scratch_folio'
> Warning: include/linux/sunrpc/xdr.h:337 No description found for return
> value of 'xdr_stream_remaining'
> Warning: include/linux/sunrpc/xdr.h:357 No description found for return
> value of 'xdr_align_size'
> Warning: include/linux/sunrpc/xdr.h:374 No description found for return
> value of 'xdr_pad_size'
> Warning: include/linux/sunrpc/xdr.h:387 No description found for return
> value of 'xdr_stream_encode_item_present'
>
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Trond Myklebust <trondmy@kernel.org>
> Cc: Anna Schumaker <anna@kernel.org>
> Cc: Chuck Lever <chuck.lever@oracle.com>
> Cc: Jeff Layton <jlayton@kernel.org>
> Cc: linux-nfs@vger.kernel.org
>
> include/linux/sunrpc/xdr.h | 48 +++++++++++++++++------------------
> 1 file changed, 24 insertions(+), 24 deletions(-)
>
Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
Randy, did you want me to take this one, or will you send it on to
Linus?
--
Chuck Lever
next prev parent reply other threads:[~2026-03-03 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 22:09 [PATCH] SUNRPC: xdr.h: fix all kernel-doc warnings Randy Dunlap
2026-03-03 16:37 ` Chuck Lever [this message]
2026-03-04 0:42 ` Randy Dunlap
2026-03-04 14:27 ` Chuck Lever
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=ccfa6bf5-6459-4633-bcbe-dfa487c8057b@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=trondmy@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