From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/3] nilfs2: Add kernel-doc comments to nilfs_do_roll_forward()
Date: Wed, 10 Apr 2024 16:56:27 +0900 [thread overview]
Message-ID: <20240410075629.3441-2-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <20240410075629.3441-1-konishi.ryusuke@gmail.com>
From: Yang Li <yang.lee@linux.alibaba.com>
This commit adds kernel-doc style comments with complete parameter
descriptions for the function nilfs_do_roll_forward.
Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
---
fs/nilfs2/recovery.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/nilfs2/recovery.c b/fs/nilfs2/recovery.c
index 49a70c68bf3c..e48372618ac4 100644
--- a/fs/nilfs2/recovery.c
+++ b/fs/nilfs2/recovery.c
@@ -563,6 +563,7 @@ static int nilfs_recover_dsync_blocks(struct the_nilfs *nilfs,
* checkpoint
* @nilfs: nilfs object
* @sb: super block instance
+ * @root: NILFS root instance
* @ri: pointer to a nilfs_recovery_info
*/
static int nilfs_do_roll_forward(struct the_nilfs *nilfs,
--
2.34.1
next prev parent reply other threads:[~2024-04-10 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:56 [PATCH 0/3] nilfs2: fix missing kernel-doc comments Ryusuke Konishi
2024-04-10 7:56 ` Ryusuke Konishi [this message]
2024-04-10 7:56 ` [PATCH 2/3] nilfs2: Add kernel-doc comments to nilfs_btree_convert_and_insert() Ryusuke Konishi
2024-04-10 7:56 ` [PATCH 3/3] nilfs2: Add kernel-doc comments to nilfs_remove_all_gcinodes() Ryusuke Konishi
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=20240410075629.3441-2-konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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