Re: [PATCH 0/7] MAINTAINERS: MM updates

[Shakeel Butt]

October 30, 2026 at 2:34 PM, "David Hildenbrand (Arm)" <david@xxxxxxxxxx mailto:david@xxxxxxxxxx?to=%22David%20Hildenbrand%20(Arm)%22%20%3Cdavid%40kernel.org%3E > wrote:


> 
> Hi,
> 
> several MM updates:
> 
> Make Zi Yan a THP maintainer (thanks for all your hard work over
> the years and thanks for taking on this responsibility), and perform some
> MM MAINTAINERS cleanups.
> 
> Then, start the next step of the transition from Andrew's MM tree to
> separate component trees that all get integrated into the mm-next
> integration tree.
> 
> Start routing shmem through mm/core.git, adding me as a maintainer
> primarily to pick patches.
> 
> Then, target the following components for the mm/core.git tree that I
> (co)maintain:
> 
>  - MEMORY MANAGEMENT - BALLOON
>  - MEMORY MANAGEMENT - CORE
>  - MEMORY MANAGEMENT - GUP (GET USER PAGES)
>  - MEMORY MANAGEMENT - KSM (Kernel Samepage Merging)
>  - MEMORY MANAGEMENT - MEMORY HOT(UN)PLUG
>  - MEMORY MANAGEMENT - MIGRATION
>  - MEMORY MANAGEMENT - NUMA PLACEMENT
>  - MEMORY MANAGEMENT - RMAP (REVERSE MAPPING)
>  - MEMORY MANAGEMENT - THP (TRANSPARENT HUGE PAGE)
> 
> More details in the last patch.
> 
> In the upcoming cycles we'll then route more of the other MM components
> through different trees.
> 
> Let's see how this goes, in particular with the continuous stream of
> fixes. But getting these in in a controlled way has highest priority
> right now wither way.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@xxxxxxxxxx>
> ---
> David Hildenbrand (Arm) (7):
>  MAINTAINERS: mention for-next branch in MEMORY MANAGEMENT - MEMORY MAP
>  MAINTAINERS: TMPFS (SHMEM FILESYSTEM) updates
>  MAINTAINERS: add Zi Yan as co-maintainer for MEMORY MANAGEMENT - THP
>  MAINTAINERS: sort entries in MM sections
>  MAINTAINERS: add missing files to MM component sections
>  MAINTAINERS: rename and move MEMORY HOT(UN)PLUG
>  MAINTAINERS: route more MM changes through mm/core.git

For the whole series:

Acked-by: Shakeel Butt <shakeel.butt@xxxxxxxxx>