linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	maple-tree@lists.infradead.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] maple_tree: Mark three functions as __maybe_unused
Date: Sat, 7 Sep 2024 19:31:14 +0100	[thread overview]
Message-ID: <f9b2b03b-24b9-49be-825f-7eb1aea59bee@lucifer.local> (raw)
In-Reply-To: <20240907021506.4018676-1-Liam.Howlett@oracle.com>

On Fri, Sep 06, 2024 at 10:15:06PM GMT, Liam R. Howlett wrote:
> People keep trying to remove three functions that are going to be used
> in a feature that is being developed.  Dropping the functions entirely
> may end up with people trying to use the bit for other uses, as people
> have tried in the past.
>
> Adding __maybe_unused stops compilers complaining about the unused
> functions so they can be silently optimised out of the compiled code and
> people won't try to claim the bit for another use.
>
> Link: https://lore.kernel.org/all/20230726080916.17454-2-zhangpeng.00@bytedance.com/
> Link: https://lore.kernel.org/all/202408310728.S7EE59BN-lkp@intel.com/
> Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>

Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>

> ---
>  lib/maple_tree.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lib/maple_tree.c b/lib/maple_tree.c
> index 4f34e50c92b5..20990ecba2dd 100644
> --- a/lib/maple_tree.c
> +++ b/lib/maple_tree.c
> @@ -348,17 +348,17 @@ 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)
> +static inline void __maybe_unused *mte_set_full(const struct maple_enode *node)
>  {
>  	return (void *)((unsigned long)node & ~MAPLE_ENODE_NULL);
>  }
>
> -static inline void *mte_clear_full(const struct maple_enode *node)
> +static inline void __maybe_unused *mte_clear_full(const struct maple_enode *node)
>  {
>  	return (void *)((unsigned long)node | MAPLE_ENODE_NULL);
>  }
>
> -static inline bool mte_has_null(const struct maple_enode *node)
> +static inline bool __maybe_unused mte_has_null(const struct maple_enode *node)
>  {
>  	return (unsigned long)node & MAPLE_ENODE_NULL;
>  }
> --
> 2.43.0
>


  reply	other threads:[~2024-09-07 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07  2:15 Liam R. Howlett
2024-09-07 18:31 ` Lorenzo Stoakes [this message]
2024-09-07 19:16   ` Kuan-Wei Chiu

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=f9b2b03b-24b9-49be-825f-7eb1aea59bee@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.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