From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>
Cc: "Liam R. Howlett" <liam@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>, Zi Yan <ziy@nvidia.com>
Subject: [PATCH v2 1/2] mm/Kconfig: make FLATMEM depend on !NUMA
Date: Wed, 5 Aug 2026 00:11:41 +0900 [thread overview]
Message-ID: <20260804151145.3419768-2-ekffu200098@gmail.com> (raw)
In-Reply-To: <20260804151145.3419768-1-ekffu200098@gmail.com>
FLATMEM + NUMA is not supported by any architecture and fails to build.
The constraint is only implicit in the arch Kconfig files.
So make it explicit in mm/Kconfig.
No functional change.
Suggested-by: Zi Yan <ziy@nvidia.com>
Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
---
mm/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/Kconfig b/mm/Kconfig
index 060190e12bce..331daf7fcfab 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -390,6 +390,7 @@ choice
config FLATMEM_MANUAL
bool "Flat Memory"
+ depends on !NUMA
depends on !ARCH_SPARSEMEM_ENABLE || ARCH_FLATMEM_ENABLE
help
This option is best suited for non-NUMA systems with
@@ -424,6 +425,7 @@ config SPARSEMEM
config FLATMEM
def_bool y
+ depends on !NUMA
depends on !SPARSEMEM || FLATMEM_MANUAL
#
--
2.43.0
next prev parent reply other threads:[~2026-08-04 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 15:11 [PATCH v2 0/2] mm/page_ext: remove pgdat_page_ext_init() Sang-Heon Jeon
2026-08-04 15:11 ` Sang-Heon Jeon [this message]
2026-08-04 15:56 ` [PATCH v2 1/2] mm/Kconfig: make FLATMEM depend on !NUMA Zi Yan
2026-08-05 9:46 ` Mike Rapoport
2026-08-05 10:05 ` David Hildenbrand (Arm)
2026-08-04 15:11 ` [PATCH v2 2/2] mm/page_ext: remove pgdat_page_ext_init() Sang-Heon Jeon
2026-08-04 15:57 ` Zi Yan
2026-08-05 10:05 ` David Hildenbrand (Arm)
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=20260804151145.3419768-2-ekffu200098@gmail.com \
--to=ekffu200098@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=liam@infradead.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 \
--cc=ziy@nvidia.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