From: "Arnd Bergmann" <arnd@arndb.de>
To: "Mike Rapoport" <rppt@kernel.org>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Changyuan Lyu" <changyuanl@google.com>,
"David Hildenbrand" <david@redhat.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Matthew Wilcox" <willy@infradead.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Kefeng Wang" <wangkefeng.wang@huawei.com>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Barry Song" <baohua@kernel.org>, "Jeff Xu" <jeffxu@chromium.org>,
"Wei Yang" <richard.weiyang@gmail.com>,
"Baoquan He" <bhe@redhat.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Frank van der Linden" <fvdl@google.com>,
"York Jasper Niebuhr" <yjnworkstation@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memblock: mark init_deferred_page as __init_memblock
Date: Thu, 24 Apr 2025 23:28:56 +0200 [thread overview]
Message-ID: <7fcb9e20-fd7e-4b59-9187-8993b3b163fe@app.fastmail.com> (raw)
In-Reply-To: <aAqPQgjgkPNtOElr@kernel.org>
On Thu, Apr 24, 2025, at 21:21, Mike Rapoport wrote:
> On Thu, Apr 24, 2025 at 07:29:29PM +0300, Mike Rapoport wrote:
>> On Wed, Apr 23, 2025 at 06:08:08PM +0200, Arnd Bergmann wrote:
>> It should be __init even, as well as a few other kho-memblock
>> functions.
>> I'll run some builds to make sure I'm not missing anything.
>
> Yeah, it looks like everything inside CONFIG_MEMBLOCK_KHO_SCRATCH can be
> just __init unconditionally:
Right, I tried the same patch after your earlier comments and agree
this is better than my patch.
Tested-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2025-04-24 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 16:08 Arnd Bergmann
2025-04-24 16:29 ` Mike Rapoport
2025-04-24 19:21 ` Mike Rapoport
2025-04-24 21:28 ` Arnd Bergmann [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=7fcb9e20-fd7e-4b59-9187-8993b3b163fe@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=baohua@kernel.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=david@redhat.com \
--cc=fvdl@google.com \
--cc=jeffxu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=yjnworkstation@gmail.com \
/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