From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: clm@fb.com
Cc: josef@toxicpanda.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: [PATCH] btrfs: Fix non-kernel-doc comment
Date: Mon, 7 Mar 2022 08:42:04 +0800 [thread overview]
Message-ID: <20220307004204.25417-1-jiapeng.chong@linux.alibaba.com> (raw)
Clean up the following clang-w1 warning:
fs/btrfs/space-info.c:1594: warning: This comment starts with '/**', but
isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Trye to reserve metadata bytes from the block_rsv's space.
fs/btrfs/space-info.c:1629: warning: This comment starts with '/**', but
isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Try to reserve data bytes for an allocation.
fs/btrfs/space-info.c:1468: warning: This comment starts with '/**', but
isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Try to reserve bytes from the block_rsv's space.
fs/btrfs/space-info.c:1375: warning: This comment starts with '/**', but
isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Do the appropriate flushing and waiting for a ticket.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
fs/btrfs/space-info.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/btrfs/space-info.c b/fs/btrfs/space-info.c
index 9652dd042c20..37b3b6f107ee 100644
--- a/fs/btrfs/space-info.c
+++ b/fs/btrfs/space-info.c
@@ -1372,7 +1372,7 @@ static void wait_reserve_ticket(struct btrfs_fs_info *fs_info,
}
/**
- * Do the appropriate flushing and waiting for a ticket
+ * handle_reserve_ticket - Do the appropriate flushing and waiting for a ticket
*
* @fs_info: the filesystem
* @space_info: space info for the reservation
@@ -1465,7 +1465,7 @@ static inline bool can_steal(enum btrfs_reserve_flush_enum flush)
}
/**
- * Try to reserve bytes from the block_rsv's space
+ * __reserve_bytes - Try to reserve bytes from the block_rsv's space
*
* @fs_info: the filesystem
* @space_info: space info we want to allocate from
@@ -1591,7 +1591,8 @@ static int __reserve_bytes(struct btrfs_fs_info *fs_info,
}
/**
- * Trye to reserve metadata bytes from the block_rsv's space
+ * btrfs_reserve_metadata_bytes - Trye to reserve metadata bytes from
+ * the block_rsv's space
*
* @fs_info: the filesystem
* @block_rsv: block_rsv we're allocating for
@@ -1626,7 +1627,7 @@ int btrfs_reserve_metadata_bytes(struct btrfs_fs_info *fs_info,
}
/**
- * Try to reserve data bytes for an allocation
+ * btrfs_reserve_data_bytes - Try to reserve data bytes for an allocation
*
* @fs_info: the filesystem
* @bytes: number of bytes we need
--
2.20.1.7.g153144c
next reply other threads:[~2022-03-07 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 0:42 Jiapeng Chong [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-18 10:13 [PATCH] btrfs: Fix non-kernel-doc comment Jiapeng Chong
2022-02-18 13:06 ` David Sterba
2022-02-15 3:34 Jiapeng Chong
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=20220307004204.25417-1-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=abaci@linux.alibaba.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.