From: Al Viro <viro@zeniv.linux.org.uk>
To: Adarsh Das <adarshdas950@gmail.com>
Cc: brauner@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ufs: add missing parameter documentation for ufs_getfrag_block
Date: Wed, 11 Feb 2026 02:40:13 +0000 [thread overview]
Message-ID: <20260211024013.GM3183987@ZenIV> (raw)
In-Reply-To: <20260209172435.58647-1-adarshdas950@gmail.com>
On Mon, Feb 09, 2026 at 10:54:35PM +0530, Adarsh Das wrote:
> Add kernel-doc descriptions for ufs_getfrag_block to fix build warnings.
Guess I'll grab it - I've got a minor UFS pile this cycle, so...
prev parent reply other threads:[~2026-02-11 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 17:24 [PATCH] ufs: add missing parameter documentation for ufs_getfrag_block Adarsh Das
2026-02-11 2:40 ` Al Viro [this message]
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=20260211024013.GM3183987@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox