From: Uladzislau Rezki <urezki@gmail.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] mm/vmalloc.c: Fix "unused function" warning
Date: Tue, 1 Feb 2022 09:30:18 +0100 [thread overview]
Message-ID: <YfjvmuzHtslp/Jao@pc638.lan> (raw)
In-Reply-To: <20220129034652.75359-1-jiapeng.chong@linux.alibaba.com>
> compute_subtree_max_size() is unused, when building with
> DEBUG_AUGMENT_PROPAGATE_CHECK=y.
>
Nit: vice versa? It is only used when DEBUG_AUGMENT_PROPAGATE_CHECK=y
> mm/vmalloc.c:785:1: warning: unused function 'compute_subtree_max_size'
> [-Wunused-function].
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> mm/vmalloc.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 028ce2b9bbf9..42d37b4bd351 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -778,17 +778,6 @@ get_subtree_max_size(struct rb_node *node)
> return va ? va->subtree_max_size : 0;
> }
>
> -/*
> - * Gets called when remove the node and rotate.
> - */
> -static __always_inline unsigned long
> -compute_subtree_max_size(struct vmap_area *va)
> -{
> - return max3(va_size(va),
> - get_subtree_max_size(va->rb_node.rb_left),
> - get_subtree_max_size(va->rb_node.rb_right));
> -}
> -
> RB_DECLARE_CALLBACKS_MAX(static, free_vmap_area_rb_augment_cb,
> struct vmap_area, rb_node, unsigned long, subtree_max_size, va_size)
>
> @@ -978,6 +967,17 @@ unlink_va(struct vmap_area *va, struct rb_root *root)
> }
>
> #if DEBUG_AUGMENT_PROPAGATE_CHECK
> +/*
> + * Gets called when remove the node and rotate.
> + */
> +static __always_inline unsigned long
> +compute_subtree_max_size(struct vmap_area *va)
> +{
> + return max3(va_size(va),
> + get_subtree_max_size(va->rb_node.rb_left),
> + get_subtree_max_size(va->rb_node.rb_right));
> +}
> +
> static void
> augment_tree_propagate_check(void)
> {
> --
> 2.20.1.7.g153144c
>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Vlad Rezki
prev parent reply other threads:[~2022-02-01 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 3:46 Jiapeng Chong
2022-02-01 8:30 ` Uladzislau Rezki [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=YfjvmuzHtslp/Jao@pc638.lan \
--to=urezki@gmail.com \
--cc=abaci@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=jiapeng.chong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox