mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Sidhartha Kumar <sidhartha.kumar@oracle.com>,
	<linux-kernel@vger.kernel.org>, <maple-tree@lists.infradead.org>
Cc: <akpm@linux-foundation.org>, <liam.howlett@oracle.com>
Subject: Re: [PATCH] maple_tree: remove struct maple_alloc
Date: Thu, 4 Dec 2025 10:56:47 +0800	[thread overview]
Message-ID: <aa05307f-494e-9c68-3cc0-6fe78bbffd63@huawei.com> (raw)
In-Reply-To: <20251203224511.469978-1-sidhartha.kumar@oracle.com>



On 2025/12/4 6:45, Sidhartha Kumar wrote:
> struct maple_alloc is deprecated after the maple tree conversion to sheaves,
> remove the references from the header file.
> 
> Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
> ---
>  include/linux/maple_tree.h | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/include/linux/maple_tree.h b/include/linux/maple_tree.h
> index 66f98a3da8d8..1323c28a7470 100644
> --- a/include/linux/maple_tree.h
> +++ b/include/linux/maple_tree.h
> @@ -129,13 +129,6 @@ struct maple_arange_64 {
>  	struct maple_metadata meta;
>  };
>  
> -struct maple_alloc {
> -	unsigned long total;
> -	unsigned char node_count;
> -	unsigned int request_count;
> -	struct maple_alloc *slot[MAPLE_ALLOC_SLOTS];
> -};
> -
>  struct maple_topiary {
>  	struct maple_pnode *parent;
>  	struct maple_enode *next; /* Overlaps the pivot */
> @@ -306,7 +299,6 @@ struct maple_node {
>  		};
>  		struct maple_range_64 mr64;
>  		struct maple_arange_64 ma64;
> -		struct maple_alloc alloc;


Reviewed-by: Jinjie Ruan <ruanjinjie@huawei.com>

>  	};
>  };
>  

  reply	other threads:[~2025-12-04  2:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 22:45 Sidhartha Kumar
2025-12-04  2:56 ` Jinjie Ruan [this message]
2025-12-16 21:32 ` 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=aa05307f-494e-9c68-3cc0-6fe78bbffd63@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=liam.howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=sidhartha.kumar@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®