From: Kriish Sharma <kriish.sharma2006@gmail.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
david.hunter.linux@gmail.com, skhan@linuxfoundation.org,
Kriish Sharma <kriish.sharma2006@gmail.com>
Subject: [PATCH] fs: doc: describe 'pinned' parameter in do_lock_mount()
Date: Wed, 24 Sep 2025 19:36:11 +0000 [thread overview]
Message-ID: <20250924193611.673838-1-kriish.sharma2006@gmail.com> (raw)
The kernel-doc comment for do_lock_mount() was missing a description
for the 'pinned' parameter:
Warning: fs/namespace.c:2772 function parameter 'pinned' not described
in 'do_lock_mount'
This patch adds a short description:
@pinned: receives the pinned mountpoint
to fix the warning and improve documentation clarity.
Signed-off-by: Kriish Sharma <kriish.sharma2006@gmail.com>
---
fs/namespace.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/namespace.c b/fs/namespace.c
index 51f77c65c0c6..4de1a33ab516 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -2738,6 +2738,7 @@ static int attach_recursive_mnt(struct mount *source_mnt,
/**
* do_lock_mount - lock mount and mountpoint
* @path: target path
+ * @pinned: receives the pinned mountpoint
* @beneath: whether the intention is to mount beneath @path
*
* Follow the mount stack on @path until the top mount @mnt is found. If
--
2.34.1
next reply other threads:[~2025-09-24 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 19:36 Kriish Sharma [this message]
2025-09-24 20:57 ` [PATCH] fs: doc: describe 'pinned' parameter in do_lock_mount() Al Viro
2025-09-24 21:22 ` Al Viro
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=20250924193611.673838-1-kriish.sharma2006@gmail.com \
--to=kriish.sharma2006@gmail.com \
--cc=brauner@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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).