From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Wei Yang <richard.weiyang@gmail.com>,
maple-tree@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH] maple_tree: fix comment typo on ma_flag of allocation tree
Date: Sun, 1 Sep 2024 00:39:30 +0000 [thread overview]
Message-ID: <20240901003930.zgwf2ijohgdugsvo@master> (raw)
In-Reply-To: <hjfufgsvcq5myikbh6h66sa4irv2wm6gwnmffzaerzeehkg5tn@uuhxbbx74j2k>
On Tue, Aug 13, 2024 at 09:29:32PM -0400, Liam R. Howlett wrote:
>* Wei Yang <richard.weiyang@gmail.com> [240808 22:02]:
>> The maple tree flag of allocation tree is MT_FLAGS_ALLOC_RANGE.
>>
>> Just correct it.
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>
>Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
>
Andrew
Sorry for not including you for this thread.
>> ---
>> include/linux/maple_tree.h | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/include/linux/maple_tree.h b/include/linux/maple_tree.h
>> index a53ad4dabd7e..9c5fd645aa0e 100644
>> --- a/include/linux/maple_tree.h
>> +++ b/include/linux/maple_tree.h
>> @@ -52,9 +52,9 @@
>> * bit in the node type. This is possible by using bit 1 to indicate if bit 2
>> * is part of the type or the slot.
>> *
>> - * Once the type is decided, the decision of an allocation range type or a range
>> - * type is done by examining the immutable tree flag for the MAPLE_ALLOC_RANGE
>> - * flag.
>> + * Once the type is decided, the decision of an allocation range type or a
>> + * range type is done by examining the immutable tree flag for the
>> + * MT_FLAGS_ALLOC_RANGE flag.
>> *
>> * Node types:
>> * 0x??1 = Root
>> --
>> 2.34.1
>>
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2024-09-01 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 2:01 Wei Yang
2024-08-14 1:29 ` Liam R. Howlett
2024-09-01 0:39 ` Wei Yang [this message]
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=20240901003930.zgwf2ijohgdugsvo@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.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