From: Wei Yang <richard.weiyang@gmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org
Cc: maple-tree@lists.infradead.org, linux-mm@kvack.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH v2 0/2] Following cleanup after introduce mas_wr_store_type()
Date: Thu, 17 Oct 2024 01:58:07 +0000 [thread overview]
Message-ID: <20241017015809.23392-1-richard.weiyang@gmail.com> (raw)
Here is two cleanup after introduction of mas_wr_store_type().
Patch 1 postpone new_end calculation when needed.
Patch 2 remove a unnecessary sanity check in mas_wr_slot_store().
v2: add a WARN_ON_ONCE() as suggested by Liam in patch 2
Wei Yang (2):
maple_tree: calculate new_end when needed
maple_tree: remove sanity check from mas_wr_slot_store()
lib/maple_tree.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2024-10-17 1:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 1:58 Wei Yang [this message]
2024-10-17 1:58 ` [PATCH v2 1/2] maple_tree: calculate new_end when needed Wei Yang
2024-10-17 1:58 ` [PATCH v2 2/2] maple_tree: remove sanity check from mas_wr_slot_store() Wei Yang
2024-10-17 2:04 ` 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=20241017015809.23392-1-richard.weiyang@gmail.com \
--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