From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/3] nilfs2: fix missing struct keywords in nilfs2_api.h kernel-doc
Date: Sat, 20 Dec 2025 03:04:27 +0900 [thread overview]
Message-ID: <20251219180631.27554-4-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <20251219180631.27554-1-konishi.ryusuke@gmail.com>
Eliminate the following kernel-doc warnings in nilfs2_api.h:
Warning: include/uapi/linux/nilfs2_api.h:65 cannot understand function
prototype: 'struct nilfs_suinfo'
Warning: include/uapi/linux/nilfs2_api.h:101 cannot understand function
prototype: 'struct nilfs_suinfo_update'
This ensures that the documentation for nilfs_suinfo and
nilfs_suinfo_update is correctly parsed and generated by adding the
missing 'struct' keyword to their kernel-doc comments.
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
---
include/uapi/linux/nilfs2_api.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/nilfs2_api.h b/include/uapi/linux/nilfs2_api.h
index 8b9b89104f3d..d1b6fcde2fb8 100644
--- a/include/uapi/linux/nilfs2_api.h
+++ b/include/uapi/linux/nilfs2_api.h
@@ -58,7 +58,7 @@ NILFS_CPINFO_FNS(INVALID, invalid)
NILFS_CPINFO_FNS(MINOR, minor)
/**
- * nilfs_suinfo - segment usage information
+ * struct nilfs_suinfo - segment usage information
* @sui_lastmod: timestamp of last modification
* @sui_nblocks: number of written blocks in segment
* @sui_flags: segment usage flags
@@ -93,7 +93,7 @@ static inline int nilfs_suinfo_clean(const struct nilfs_suinfo *si)
}
/**
- * nilfs_suinfo_update - segment usage information update
+ * struct nilfs_suinfo_update - segment usage information update
* @sup_segnum: segment number
* @sup_flags: flags for which fields are active in sup_sui
* @sup_reserved: reserved necessary for alignment
--
2.43.0
next prev parent reply other threads:[~2025-12-19 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 18:04 [PATCH 0/3] nilfs2 fixes on v6.19-rc1 Ryusuke Konishi
2025-12-19 18:04 ` [PATCH 1/3] nilfs2: Fix potential block overflow that cause system hang Ryusuke Konishi
2025-12-19 18:04 ` [PATCH 2/3] nilfs2: convert nilfs_super_block to kernel-doc Ryusuke Konishi
2025-12-19 18:04 ` Ryusuke Konishi [this message]
2025-12-23 0:16 ` [PATCH 0/3] nilfs2 fixes on v6.19-rc1 Viacheslav Dubeyko
2025-12-23 3:32 ` 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=20251219180631.27554-4-konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.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