From: Mike Rapoport <rppt@kernel.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Kaitao Cheng <kaitao.cheng@linux.dev>,
Priyanshu Kumar <priyanshukumarpu@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] memblock: Remove unused exact nid allocation API
Date: Tue, 13 Oct 2026 20:27:25 +0300 [thread overview]
Message-ID: <as5p_av2Y0Hu70_2@kernel.org> (raw)
In-Reply-To: <35057B7F-9E89-447B-AF4F-92A78B45F8E2@linux.dev>
On Tue, Oct 13, 2026 at 06:06:49PM +0800, Muchun Song wrote:
> > On Oct 13, 2026, at 17:50, Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Sat, 19 Sep 2026 21:53:24 +0800, Kaitao Cheng wrote:
> >> memblock: Remove unused exact nid allocation API
> >>
> >> Commit ffe55393137c ("mm/sparse: remove sparse buffer pre-allocation
> >> mechanism") removed the only memmap_alloc() caller that requested an
> >> allocation from an exact NUMA node. All remaining callers allow fallback
> >> to other nodes, leaving the exact_nid argument unused.
> >>
> >> [...]
> >
> > Applied to for-next branch of memblock.git tree, thanks!
> >
> > [1/3] mm: Remove unused exact_nid parameter from memmap_alloc()
> > commit: 063b5e8bbd216c27e885f45e29e23d053aa565fc
> > [2/3] memblock tests: Move exact nid tests to memblock_alloc_range_nid()
> > commit: fba3e86fb848f79c4573243affcd7d79d378958d
> > [3/3] memblock: Remove unused memblock_alloc_exact_nid_raw()
> > commit: ea27be9f7ce90a05e779d20b60969ce2a9834f77
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
> > branch: for-next
>
> Hi Mike,
>
> Just a heads-up, the tree has moved to:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mm/memblock
>
> Might want to update it next time.
Yep, thanks!
> Cheers,
> Muchun
>
> >
> > --
> > Sincerely yours,
> > Mike.
> >
> >
>
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-10-13 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 13:53 [PATCH v2 0/3] memblock: Remove unused exact nid allocation API Kaitao Cheng
2026-09-19 13:53 ` [PATCH v2 1/3] mm: Remove unused exact_nid parameter from memmap_alloc() Kaitao Cheng
2026-09-19 13:53 ` [PATCH v2 2/3] memblock tests: Move exact nid tests to memblock_alloc_range_nid() Kaitao Cheng
2026-09-19 13:53 ` [PATCH v2 3/3] memblock: Remove unused memblock_alloc_exact_nid_raw() Kaitao Cheng
2026-09-24 7:48 ` [PATCH v2 0/3] memblock: Remove unused exact nid allocation API Mike Rapoport
2026-10-12 3:06 ` Kaitao Cheng
2026-10-13 9:50 ` Mike Rapoport
2026-10-13 10:06 ` Muchun Song
2026-10-13 17:27 ` Mike Rapoport [this message]
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=as5p_av2Y0Hu70_2@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=kaitao.cheng@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=priyanshukumarpu@gmail.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.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