From: Peng Zhang <zhangpeng.00@bytedance.com>
To: Liam.Howlett@oracle.com, dan.carpenter@linaro.org,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
maple-tree@lists.infradead.org,
Peng Zhang <zhangpeng.00@bytedance.com>
Subject: [PATCH v2 0/5] Some cleanups of maple tree
Date: Mon, 20 Nov 2023 15:09:32 +0800 [thread overview]
Message-ID: <20231120070937.35481-1-zhangpeng.00@bytedance.com> (raw)
These are some small cleanups of maple tree.
Just to mention, in v1, I forgot to CC LKML, but it has been added in this
version.
Changes since v1:
- Removed the 'return' statement from [1/5].
- Made slight modifications to the commit log of [5/5].
v1: http://lists.infradead.org/pipermail/maple-tree/2023-November/003047.html
Peng Zhang (5):
maple_tree: Move the check forward to avoid static check warning
maple_tree: Avoid ascending when mas->min is also the parent's minimum
maple_tree: Remove an unused parameter for ma_meta_end()
maple_tree: Delete one of the two identical checks
maple_tree: Simplify mas_leaf_set_meta()
lib/maple_tree.c | 45 ++++++++++++++-------------------------------
1 file changed, 14 insertions(+), 31 deletions(-)
--
2.20.1
next reply other threads:[~2023-11-20 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 7:09 Peng Zhang [this message]
2023-11-20 7:09 ` [PATCH v2 1/5] maple_tree: Move the check forward to avoid static check warning Peng Zhang
2023-11-20 7:09 ` [PATCH v2 2/5] maple_tree: Avoid ascending when mas->min is also the parent's minimum Peng Zhang
2023-11-20 7:09 ` [PATCH v2 3/5] maple_tree: Remove an unused parameter for ma_meta_end() Peng Zhang
2023-11-20 7:09 ` [PATCH v2 4/5] maple_tree: Delete one of the two identical checks Peng Zhang
2023-11-20 7:09 ` [PATCH v2 5/5] maple_tree: Simplify mas_leaf_set_meta() Peng Zhang
2023-11-20 15:43 ` [PATCH v2 0/5] Some cleanups of maple tree 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=20231120070937.35481-1-zhangpeng.00@bytedance.com \
--to=zhangpeng.00@bytedance.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@linaro.org \
--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