From: slopixelz@gmail.com
To: viro@zeniv.linux.org.uk
Cc: willy@infradead.org, brauner@kernel.org,
chentaotao@didiglobal.com, linux-kernel@vger.kernel.org,
Shubham Sharma <slopixelz@gmail.com>
Subject: [PATCH] fs/ufs: Add kernel-doc for ufs_getfrag_block()
Date: Fri, 3 Oct 2025 14:58:36 +0530 [thread overview]
Message-ID: <20251003092836.120417-1-slopixelz@gmail.com> (raw)
From: Shubham Sharma <slopixelz@gmail.com>
Fix missing parameter documentation in ufs_getfrag_block().
Kernel-doc warnings reported for 'inode','fragment', 'bh_result' and 'create'.
Add proper kernel-doc comments to describe these parameters.
---
fs/ufs/inode.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c
index 8361c00e8fa6..0776eef812fd 100644
--- a/fs/ufs/inode.c
+++ b/fs/ufs/inode.c
@@ -370,7 +370,11 @@ static u64 ufs_inode_getblock(struct inode *inode, u64 ind_block,
/**
* ufs_getfrag_block() - `get_block_t' function, interface between UFS and
* read_folio, writepages and so on
- */
+ * @inode: pointer to inode
+ * @fragment: fragment number to fetch
+ * @bh_result: pointer to buffer_head where the block mapping will be stored
+ * @create: flag indicating whether to allocate the block if it does not exist
+*/
static int ufs_getfrag_block(struct inode *inode, sector_t fragment, struct buffer_head *bh_result, int create)
{
--
2.48.1
reply other threads:[~2025-10-03 9:28 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=20251003092836.120417-1-slopixelz@gmail.com \
--to=slopixelz@gmail.com \
--cc=brauner@kernel.org \
--cc=chentaotao@didiglobal.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@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