The NUMA_BALANCING_DEFAULT_ENABLED config option is semantically
related to NUMA_BALANCING. Move it directly after its parent option
so they are grouped together, improving readability.

No functional change.

Signed-off-by: Bing Huang <huangbing@kylinos.cn>
---
 init/Kconfig | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/init/Kconfig b/init/Kconfig
index 53178ea4bc93..68f259fea239 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1019,6 +1019,14 @@ config NUMA_BALANCING
 
 	  This system will be inactive on UMA systems.
 
+config NUMA_BALANCING_DEFAULT_ENABLED
+	bool "Automatically enable NUMA aware memory/task placement"
+	default y
+	depends on NUMA_BALANCING
+	help
+	  If set, automatic NUMA balancing will be enabled if running on a NUMA
+	  machine.
+
 config SCHED_CACHE
 	bool "Cache aware load balance"
 	default y
@@ -1030,14 +1038,6 @@ config SCHED_CACHE
 	  resources within the same cache domain, reducing cache misses and
 	  lowering data access latency.
 
-config NUMA_BALANCING_DEFAULT_ENABLED
-	bool "Automatically enable NUMA aware memory/task placement"
-	default y
-	depends on NUMA_BALANCING
-	help
-	  If set, automatic NUMA balancing will be enabled if running on a NUMA
-	  machine.
-
 config SLAB_OBJ_EXT
 	bool
 
-- 
2.25.1

Hi Bing,

On 7/23/26 06:50, Bing Huang wrote:
> The NUMA_BALANCING_DEFAULT_ENABLED config option is semantically
> related to NUMA_BALANCING. Move it directly after its parent option
> so they are grouped together, improving readability.
> 
> No functional change.

Actually there is actually a minor functional difference to the Kconfig
frontend (e.g menuconfig): the prompt for this option will now be
indented below that of NUMA_BALANCING, rendered as part of its submenu.
(This is a good thing...)

Reviewed-by: Julian Braha <julianbraha@gmail.com>

Hi Julian,

Thanks for the review and the great catch about the menuconfig
indentation -- that's a nice side effect I hadn't mentioned.

I've updated the commit to include your Reviewed-by tag and expanded
the commit message to note the visual grouping change.

Thanks,
Bing