From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH -next] fs: d_path.c: fix prepend_buffer kernel-doc warnings
Date: Sun, 27 Jun 2021 18:46:13 -0700 [thread overview]
Message-ID: <20210628014613.11296-1-rdunlap@infradead.org> (raw)
Fix new kernel-doc warnings related to struct prepend_buffer:
../fs/d_path.c:52: warning: Excess function parameter 'buffer' description in 'prepend_name'
../fs/d_path.c:52: warning: Excess function parameter 'buflen' description in 'prepend_name'
../fs/d_path.c:127: warning: Excess function parameter 'buffer' description in 'prepend_path'
../fs/d_path.c:127: warning: Excess function parameter 'buflen' description in 'prepend_path'
Fixes: ad08ae586586e ("d_path: introduce struct prepend_buffer")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
---
fs/d_path.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--- linux-next-20210625.orig/fs/d_path.c
+++ linux-next-20210625/fs/d_path.c
@@ -33,8 +33,7 @@ static void prepend(struct prepend_buffe
/**
* prepend_name - prepend a pathname in front of current buffer pointer
- * @buffer: buffer pointer
- * @buflen: allocated length of the buffer
+ * @p: &struct prepend_buffer parameters
* @name: name string and length qstr structure
*
* With RCU path tracing, it may race with d_move(). Use READ_ONCE() to
@@ -108,8 +107,7 @@ static int __prepend_path(const struct d
* prepend_path - Prepend path string to a buffer
* @path: the dentry/vfsmount to report
* @root: root vfsmnt/dentry
- * @buffer: pointer to the end of the buffer
- * @buflen: pointer to buffer length
+ * @p: &struct prepend_buffer parameters
*
* The function will first try to write out the pathname without taking any
* lock other than the RCU read lock to make sure that dentries won't go away.
reply other threads:[~2021-06-28 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210628014613.11296-1-rdunlap@infradead.org \
--to=rdunlap@infradead.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).