Re: [PATCH 2/3] mm, treewide: replace __folio_alloc_node() with folio_alloc_node()

[PATCH 0/3] mm: yet more cleanups for page_alloc APIs · Brendan Jackman <jackmanb@google.com> · 2026-07-16
[PATCH 2/3] mm, treewide: replace __folio_alloc_node() with folio_alloc_node() · Brendan Jackman <jackmanb@google.com> · 2026-07-16
Re: [PATCH 2/3] mm, treewide: replace __folio_alloc_node() with folio_alloc_node() · Brendan Jackman <hidden> · 2026-07-16
[PATCH 1/3] mm: move internal mempolicy APIs to new internal header · Brendan Jackman <jackmanb@google.com> · 2026-07-16
Re: [PATCH 1/3] mm: move internal mempolicy APIs to new internal header · "Vlastimil Babka (SUSE)" <vbabka@kernel.org> · 2026-07-16
Re: [PATCH 1/3] mm: move internal mempolicy APIs to new internal header · Brendan Jackman <hidden> · 2026-07-16
Re: [PATCH 1/3] mm: move internal mempolicy APIs to new internal header · Matthew Wilcox <willy@infradead.org> · 2026-07-16
Re: [PATCH 1/3] mm: move internal mempolicy APIs to new internal header · Brendan Jackman <hidden> · 2026-07-16
[PATCH 3/3] mm: move __folio_alloc() to page_alloc.h · Brendan Jackman <jackmanb@google.com> · 2026-07-16

From: Brendan Jackman <hidden>
Date: 2026-07-16 17:00:52
Also in: linux-fsdevel, linux-iommu, linux-mm, linux-nfs, lkml, loongarch

On Thu Jul 16, 2026 at 2:30 PM UTC, Brendan Jackman wrote:

Commit 5b584d2d22dca ("mm: remove __alloc_pages_node()") removed the __

Oh, I just remembered this commit hash is unstable. In fact it's already
wrong.

variant of alloc_pages_node(), after users had been migrated off it,
since it just complicates the API (requiring users to handle
NUMA_NO_NODE, or risking hotplug bugs) for no real benefit.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help