From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Jann Horn <jannh@google.com>
Cc: maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] maple_tree: fix outdated flag name in comment
Date: Tue, 8 Oct 2024 20:10:58 -0400 [thread overview]
Message-ID: <fhsmzzdniegmipfpnqexw4dqcfbs42y77agisobf56ioeydfug@5kpgpsygissu> (raw)
In-Reply-To: <20241007-maple-tree-doc-fix-v1-1-6bbf89c1153d@google.com>
* Jann Horn <jannh@google.com> [241007 17:48]:
> MAPLE_USE_RCU was renamed to MT_FLAGS_USE_RCU at some point, fix up the
> comment.
>
> Signed-off-by: Jann Horn <jannh@google.com>
Thanks
Reviewed-by: Liam R. Howlett <Liam.Howlett@Oracle.com>
> ---
> include/linux/maple_tree.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/maple_tree.h b/include/linux/maple_tree.h
> index c2c11004085e..61c236850ca8 100644
> --- a/include/linux/maple_tree.h
> +++ b/include/linux/maple_tree.h
> @@ -224,7 +224,7 @@ typedef struct { /* nothing */ } lockdep_map_p;
> * (set at tree creation time) and dynamic information set under the spinlock.
> *
> * Another use of flags are to indicate global states of the tree. This is the
> - * case with the MAPLE_USE_RCU flag, which indicates the tree is currently in
> + * case with the MT_FLAGS_USE_RCU flag, which indicates the tree is currently in
> * RCU mode. This mode was added to allow the tree to reuse nodes instead of
> * re-allocating and RCU freeing nodes when there is a single user.
> */
>
> ---
> base-commit: 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b
> change-id: 20241007-maple-tree-doc-fix-db016fe321ce
> --
> Jann Horn <jannh@google.com>
>
>
> --
> maple-tree mailing list
> maple-tree@lists.infradead.org
> https://lists.infradead.org/mailman/listinfo/maple-tree
next prev parent reply other threads:[~2024-10-09 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 21:47 Jann Horn
2024-10-09 0:10 ` Liam R. Howlett [this message]
2024-10-11 1:43 ` Wei Yang
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=fhsmzzdniegmipfpnqexw4dqcfbs42y77agisobf56ioeydfug@5kpgpsygissu \
--to=liam.howlett@oracle.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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