cpumask-limit-visibility-of-force_nr_cpus.patch removed from -mm tree
The quilt patch titled
Subject: cpumask: limit visibility of FORCE_NR_CPUS
has been removed from the -mm tree. Its filename was
cpumask-limit-visibility-of-force_nr_cpus.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Yury Norov <[email protected]>
Subject: cpumask: limit visibility of FORCE_NR_CPUS
Date: Wed, 16 Nov 2022 09:24:51 -0800
In current form, FORCE_NR_CPUS is visible to all users building their kernels, even not experts. It is also set in allmodconfig or allyesconfig, which is not a correct behavior.
This patch fixes it. It also changes the parameter short description:
removes implementation details and highlights the effect of the change.
---
lib/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
lib/Kconfig renamed from lib/Kconfig~cpumask-limit-visibility-of-force_nr_cpus +2 -2
@@ -529,8 +529,8 @@ config CPUMASK_OFFSTACK stack overflow. config FORCE_NR_CPUS - bool "NR_CPUS is set to an actual number of CPUs" - depends on SMP + bool "Set number of CPUs at compile time" + depends on SMP && EXPERT && !COMPILE_TEST help Say Yes if you have NR_CPUS set to an actual number of possible CPUs in your system, not to a default value. This forces the core
_
Patches currently in -mm which might be from [email protected] are