From: Adarsh Das <adarshdas950@gmail.com>
To: brauner@kernel.org
Cc: linux-kernel@vger.kernel.org, Adarsh Das <adarshdas950@gmail.com>
Subject: [PATCH] ufs: add missing parameter documentation for ufs_getfrag_block
Date: Mon, 9 Feb 2026 22:54:35 +0530 [thread overview]
Message-ID: <20260209172435.58647-1-adarshdas950@gmail.com> (raw)
Add kernel-doc descriptions for ufs_getfrag_block to fix build warnings.
Signed-off-by: Adarsh Das <adarshdas950@gmail.com>
---
fs/ufs/inode.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c
index e2b0a35de2a7..f159447f53bb 100644
--- a/fs/ufs/inode.c
+++ b/fs/ufs/inode.c
@@ -370,6 +370,10 @@ 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 map
+ * @bh_result: buffer head to fill with mapping information
+ * @create: if non-zero, allocate new blocks/fragments if needed
*/
static int ufs_getfrag_block(struct inode *inode, sector_t fragment, struct buffer_head *bh_result, int create)
--
2.53.0
next reply other threads:[~2026-02-09 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 17:24 Adarsh Das [this message]
2026-02-11 2:40 ` [PATCH] ufs: add missing parameter documentation for ufs_getfrag_block 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=20260209172435.58647-1-adarshdas950@gmail.com \
--to=adarshdas950@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.