From: Wei Yang <richard.weiyang@gmail.com>
To: akpm@linux-foundation.org, Liam.Howlett@oracle.com
Cc: linux-kernel@vger.kernel.org, maple-tree@lists.infradead.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH 2/2] maple_tree: fix comment typo with corresponding maple_status
Date: Mon, 12 Aug 2024 15:09:25 +0000 [thread overview]
Message-ID: <20240812150925.31551-2-richard.weiyang@gmail.com> (raw)
In-Reply-To: <20240812150925.31551-1-richard.weiyang@gmail.com>
In comment of function mas_start(), we list the return value of
different cases. According to the comment context, tell the maple_status
here is more consistent with others.
Let's correct it with ma_active in the case it's a tree.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
---
lib/maple_tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index 14ff54078f9e..026197c44988 100644
--- a/lib/maple_tree.c
+++ b/lib/maple_tree.c
@@ -1347,7 +1347,7 @@ static void mas_node_count(struct ma_state *mas, int count)
* - If mas->node is an error or not mas_start, return NULL.
* - If it's an empty tree: NULL & mas->status == ma_none
* - If it's a single entry: The entry & mas->status == ma_root
- * - If it's a tree: NULL & mas->status == safe root node.
+ * - If it's a tree: NULL & mas->status == ma_active
*/
static inline struct maple_enode *mas_start(struct ma_state *mas)
{
--
2.34.1
next prev parent reply other threads:[~2024-08-12 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:09 [PATCH 1/2] maple_tree: fix comment typo of ma_root Wei Yang
2024-08-12 15:09 ` Wei Yang [this message]
2024-08-14 1:37 ` [PATCH 2/2] maple_tree: fix comment typo with corresponding maple_status Liam R. Howlett
2024-08-14 1:31 ` [PATCH 1/2] maple_tree: fix comment typo of ma_root Liam R. Howlett
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=20240812150925.31551-2-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maple-tree@lists.infradead.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®