From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] nilfs2: fix kernel-doc comments for function return values
Date: Thu, 9 Jan 2025 12:23:19 +0900 [thread overview]
Message-ID: <20250109032846.10147-1-konishi.ryusuke@gmail.com> (raw)
Hi Andrew,
please add this series to the queue for the next merge window.
This series fixes the inadequacies in the return value descriptions in
nilfs2's kernel-doc comments (mainly incorrect formatting), as well as
the lack of return value descriptions themselves, and fixes most of
the remaining warnings that are output when the kernel-doc script is
run with the "-Wall" option.
Thanks,
Ryusuke Konishi
Ryusuke Konishi (6):
nilfs2: correct return value kernel-doc descriptions for ioctl
functions
nilfs2: correct return value kernel-doc descriptions for bmap
functions
nilfs2: correct return value kernel-doc descriptions for sufile
nilfs2: correct return value kernel-doc descriptions for metadata
files
nilfs2: correct return value kernel-doc descriptions for the rest
nilfs2: add missing return value kernel-doc descriptions
fs/nilfs2/alloc.c | 64 +++++++++++-
fs/nilfs2/alloc.h | 2 +
fs/nilfs2/bmap.c | 113 +++++++++-------------
fs/nilfs2/btree.c | 7 +-
fs/nilfs2/cpfile.c | 49 ++++------
fs/nilfs2/dat.c | 39 +++-----
fs/nilfs2/gcinode.c | 22 ++---
fs/nilfs2/ifile.c | 32 +++---
fs/nilfs2/inode.c | 16 ++-
fs/nilfs2/ioctl.c | 220 ++++++++++++++++--------------------------
fs/nilfs2/mdt.c | 59 ++++++-----
fs/nilfs2/page.c | 8 +-
fs/nilfs2/recovery.c | 57 +++++++----
fs/nilfs2/segbuf.c | 12 +--
fs/nilfs2/segment.c | 53 +++++-----
fs/nilfs2/sufile.c | 104 ++++++++------------
fs/nilfs2/sufile.h | 21 ++--
fs/nilfs2/super.c | 10 +-
fs/nilfs2/the_nilfs.c | 25 +++--
19 files changed, 428 insertions(+), 485 deletions(-)
--
2.43.0
next reply other threads:[~2025-01-09 3:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 3:23 Ryusuke Konishi [this message]
2025-01-09 3:23 ` [PATCH 1/6] nilfs2: correct return value kernel-doc descriptions for ioctl functions Ryusuke Konishi
2025-01-09 13:44 ` Brian G.
2025-01-09 14:38 ` Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 0/7] nilfs2: fix kernel-doc comments for function return values Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 1/7] nilfs2: correct return value kernel-doc descriptions for ioctl functions Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 2/7] nilfs2: correct return value kernel-doc descriptions for bmap functions Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 3/7] nilfs2: correct return value kernel-doc descriptions for sufile Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 4/7] nilfs2: correct return value kernel-doc descriptions for metadata files Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 5/7] nilfs2: correct return value kernel-doc descriptions for the rest Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 6/7] nilfs2: add missing return value kernel-doc descriptions Ryusuke Konishi
2025-01-10 1:01 ` [PATCH -v2 7/7] nilfs2: revise the return value description style for consistency Ryusuke Konishi
2025-01-09 3:23 ` [PATCH 2/6] nilfs2: correct return value kernel-doc descriptions for bmap functions Ryusuke Konishi
2025-01-09 3:23 ` [PATCH 3/6] nilfs2: correct return value kernel-doc descriptions for sufile Ryusuke Konishi
2025-01-09 3:23 ` [PATCH 4/6] nilfs2: correct return value kernel-doc descriptions for metadata files Ryusuke Konishi
2025-01-09 3:23 ` [PATCH 5/6] nilfs2: correct return value kernel-doc descriptions for the rest Ryusuke Konishi
2025-01-09 3:23 ` [PATCH 6/6] nilfs2: add missing return value kernel-doc descriptions 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=20250109032846.10147-1-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
all inboxes | Powered by JetHome®