Re: [PATCH] drivers/base, mm: move arch_numa.c to mm/
Andrew Morton <[email protected]>
| Newsgroups | org.infradead.lists.linux-riscv,dev.linux.lists.driver-core,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 06 Aug 2026 09:58:38 +0300 "Mike Rapoport (Microsoft)" <[email protected]> wrote: > arch_numa.c implements boot time discovery and initialization of NUMA > topology on architectures that select GENERIC_ARCH_NUMA (currently arm64 > and riscv). > > Since this is step in the initialization of the memory management > subsystem, it's logical to have arch_numa.c in mm/ alongside numa.c, > numa_memblks.c and numa_emulation.c. > > Move arch_numa.c to mm/ and add its F: entry to "MEMBLOCK AND MEMORY > MANAGEMENT INITIALIZATION" in MAINTAINERS. Unclear what tree this is targeted at. I grabbed it. mm-stable does have this change: --- linux-7.2-rc5/drivers/base/arch_numa.c 2026-07-27 04:44:55.000000000 -0700 +++ 25/drivers/base/arch_numa.c 2026-08-06 15:47:59.019918702 -0700 @@ -231,10 +231,6 @@ static int __init numa_init(int (*init_f { int ret; - nodes_clear(numa_nodes_parsed); - nodes_clear(node_possible_map); - nodes_clear(node_online_map); - ret = numa_memblks_init(init_func, /* memblock_force_top_down */ false); if (ret < 0) goto out_free_distance; which is easily handled either way. _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv