All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: linux-sh@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Mike Rapoport <rppt@kernel.org>, Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH v2 07/10] init/Kconfig: drop ARCH_WANT_NUMA_VARIABLE_LOCALITY
Date: Sun, 10 May 2026 16:55:43 +0300	[thread overview]
Message-ID: <20260510135546.13554-8-rppt@kernel.org> (raw)
In-Reply-To: <20260510135546.13554-1-rppt@kernel.org>

From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>

sh was the only architecture that selected ARCH_WANT_NUMA_VARIABLE_LOCALITY.

With NUMA support on sh gone, there is no need in this configuration
option.

Remove it.

Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
---
 init/Kconfig | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/init/Kconfig b/init/Kconfig
index 2937c4d308ae..33337fde1197 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1001,16 +1001,9 @@ config CC_STRINGOP_OVERFLOW
 config ARCH_SUPPORTS_INT128
 	bool
 
-# For architectures that (ab)use NUMA to represent different memory regions
-# all cpu-local but of different latencies, such as SuperH.
-#
-config ARCH_WANT_NUMA_VARIABLE_LOCALITY
-	bool
-
 config NUMA_BALANCING
 	bool "Memory placement aware NUMA scheduler"
 	depends on ARCH_SUPPORTS_NUMA_BALANCING
-	depends on !ARCH_WANT_NUMA_VARIABLE_LOCALITY
 	depends on SMP && NUMA_MIGRATION && !PREEMPT_RT
 	help
 	  This option adds support for automatic NUMA aware memory/task placement.
-- 
2.53.0



  parent reply	other threads:[~2026-05-10 13:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 13:55 [PATCH v2 00/10] sh: remove NUMA and SPARSEMEM support Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 01/10] sh: remove CONFIG_NUMA and realted configuration options Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 02/10] sh: mm: remove numa.c Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 03/10] sh: mm: drop allocate_pgdat() Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 04/10] sh: remove setup_bootmem_node() and plat_mem_setup() Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 05/10] sh: drop dead code guarded by #ifdef CONFIG_NUMA Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 06/10] sh: drop include/asm/mmzone.h Mike Rapoport
2026-05-10 13:55 ` Mike Rapoport [this message]
2026-05-10 13:55 ` [PATCH v2 08/10] sh: init: remove call the memblock_set_node() Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 09/10] sh: remove SPARSEMEM related entries from Kconfig Mike Rapoport
2026-05-10 13:55 ` [PATCH v2 10/10] sh: drop include/asm/sparsemem.h Mike Rapoport
2026-05-18 11:43 ` [PATCH v2 00/10] sh: remove NUMA and SPARSEMEM support Mike Rapoport
2026-05-18 12:05   ` John Paul Adrian Glaubitz
2026-06-03 15:32     ` Mike Rapoport

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=20260510135546.13554-8-rppt@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.