From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: Liam.Howlett@oracle.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: [PATCH] Maple Tree: Remove unused functions mte_set_full and mte_clear_full
Date: Wed, 14 Sep 2022 18:18:29 +0800 [thread overview]
Message-ID: <20220914101829.82000-1-jiapeng.chong@linux.alibaba.com> (raw)
mte_set_full and mte_clear_full are defined in the maple_tree.c file,
but not called elsewhere, so delete these unused function.
lib/maple_tree.c:330:20: warning: unused function 'mte_set_full'.
lib/maple_tree.c:335:20: warning: unused function 'mte_clear_full'.
Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2156
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
lib/maple_tree.c | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index e1743803c851..e31b5b1f71d7 100644
--- a/lib/maple_tree.c
+++ b/lib/maple_tree.c
@@ -327,16 +327,6 @@ static inline void *mte_safe_root(const struct maple_enode *node)
return (void *)((unsigned long)node & ~MAPLE_ROOT_NODE);
}
-static inline void mte_set_full(const struct maple_enode *node)
-{
- node = (void *)((unsigned long)node & ~MAPLE_ENODE_NULL);
-}
-
-static inline void mte_clear_full(const struct maple_enode *node)
-{
- node = (void *)((unsigned long)node | MAPLE_ENODE_NULL);
-}
-
static inline bool ma_is_root(struct maple_node *node)
{
return ((unsigned long)node->parent & MA_ROOT_PARENT);
--
2.20.1.7.g153144c
next reply other threads:[~2022-09-14 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 10:18 Jiapeng Chong [this message]
2022-09-14 10:20 ` [PATCH] Maple Tree: Remove unused functions mte_set_full and mte_clear_full Matthew Wilcox
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=20220914101829.82000-1-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=Liam.Howlett@oracle.com \
--cc=abaci@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.