From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,zhanxusheng@xiaomi.com,liam@infradead.org,andrewjballance@gmail.com,aliceryhl@google.com,zhanxusheng1024@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] maple_tree-remove-unused-mas_is_root_limits.patch removed from -mm tree
Date: Mon, 24 Aug 2026 18:54:19 -0700 [thread overview]
Message-ID: <20260825015419.76B221F00A3A@smtp.kernel.org> (raw)
The quilt patch titled
Subject: maple_tree: remove unused mas_is_root_limits()
has been removed from the -mm tree. Its filename was
maple_tree-remove-unused-mas_is_root_limits.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Zhan Xusheng <zhanxusheng1024@gmail.com>
Subject: maple_tree: remove unused mas_is_root_limits()
Date: Wed, 5 Aug 2026 15:05:29 +0800
The last callers of mas_is_root_limits() were removed by commit
b8852ef30c67 ("maple_tree: remove maple big node and subtree structs"),
together with the maple subtree state (mast_*) code that used it. As a
static inline it does not trigger -Wunused-function, so it went unnoticed.
Remove it. No functional change.
Link: https://lore.kernel.org/20260805070529.4118794-1-zhanxusheng@xiaomi.com
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
Reviewed-by: Liam R. Howlett (Oracle) <liam@infradead.org>
Cc: Alice Ryhl <aliceryhl@google.com>
Cc: Andrew Ballance <andrewjballance@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/maple_tree.c | 5 -----
1 file changed, 5 deletions(-)
--- a/lib/maple_tree.c~maple_tree-remove-unused-mas_is_root_limits
+++ a/lib/maple_tree.c
@@ -356,11 +356,6 @@ static __always_inline bool mte_is_root(
return ma_is_root(mte_to_node(node));
}
-static inline bool mas_is_root_limits(const struct ma_state *mas)
-{
- return !mas->min && mas->max == ULONG_MAX;
-}
-
static __always_inline bool mt_is_alloc(struct maple_tree *mt)
{
return (mt->ma_flags & MT_FLAGS_ALLOC_RANGE);
_
Patches currently in -mm which might be from zhanxusheng1024@gmail.com are
reply other threads:[~2026-08-25 1:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260825015419.76B221F00A3A@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=andrewjballance@gmail.com \
--cc=liam@infradead.org \
--cc=mm-commits@vger.kernel.org \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.