From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: David Hildenbrand <david@kernel.org>, Kees Cook <kees@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] memblock: move reserve_bootmem_range() to memblock.c and make it static
Date: Sun, 22 Mar 2026 09:38:00 -0700 [thread overview]
Message-ID: <20260322093800.27f8b2d249817270bcc6a437@linux-foundation.org> (raw)
In-Reply-To: <20260322143144.3540679-1-rppt@kernel.org>
On Sun, 22 Mar 2026 16:31:44 +0200 Mike Rapoport <rppt@kernel.org> wrote:
> reserve_bootmem_range() is only called from memmap_init_reserved_pages()
> and it was in mm/mm_init.c because of its dependecies on static
> init_deferred_pages().
>
> Since init_deferred_pages() is not static anymore, move
> reserve_bootmem_range(), rename it to memmap_init_reserved_range() and
> make it static.
>
> Update the comment describing it to better reflect what the function
> does and drop bogus comment about reserved pages in free_bootmem_page().
>
> Update memblock test stubs to reflect the core changes.
Some minor observations from Sashiko:
https://sashiko.dev/#/patchset/20260322143144.3540679-1-rppt@kernel.org
prev parent reply other threads:[~2026-03-22 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 14:31 [PATCH] memblock: move reserve_bootmem_range() to memblock.c and make it static Mike Rapoport
2026-03-22 16:38 ` Andrew Morton [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=20260322093800.27f8b2d249817270bcc6a437@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=david@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--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