From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Yang Li <yang.lee@linux.alibaba.com>, akpm <akpm@linux-foundation.org>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] fs: Add kernel-doc comments to ocfs2_prepare_orphan_dir()
Date: Fri, 22 Mar 2024 20:41:24 +0800 [thread overview]
Message-ID: <23f6cc23-9f9b-405b-8c8e-5cda14e79587@linux.alibaba.com> (raw)
In-Reply-To: <20240322063718.88183-1-yang.lee@linux.alibaba.com>
On 3/22/24 2:37 PM, Yang Li wrote:
> This commit adds kernel-doc style comments with complete parameter
> descriptions for the function ocfs2_prepare_orphan_dir.
>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/namei.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c
> index 9221a33f917b..8a61c5f94533 100644
> --- a/fs/ocfs2/namei.c
> +++ b/fs/ocfs2/namei.c
> @@ -2187,8 +2187,10 @@ static int __ocfs2_prepare_orphan_dir(struct inode *orphan_dir_inode,
> * @osb: ocfs2 file system
> * @ret_orphan_dir: Orphan dir inode - returned locked!
> * @blkno: Actual block number of the inode to be inserted into orphan dir.
> + * @name: Buffer to store the name of the orphan.
> * @lookup: dir lookup result, to be passed back into functions like
> * ocfs2_orphan_add
> + * @dio: Flag indicating if direct IO is being used or not.
> *
> * Returns zero on success and the ret_orphan_dir, name and lookup
> * fields will be populated.
prev parent reply other threads:[~2024-03-22 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 6:37 [PATCH -next] fs: Add kernel-doc comments to ocfs2_prepare_orphan_dir() Yang Li
2024-03-22 12:41 ` Joseph Qi [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=23f6cc23-9f9b-405b-8c8e-5cda14e79587@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
--cc=yang.lee@linux.alibaba.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).