Re: [PATCH] cpumask: limit visibility of FORCE_NR_CPUS

[Yury Norov]

On Wed, Oct 19, 2022 at 02:22:40PM +0300, Andy Shevchenko wrote:
> On Tue, Oct 18, 2022 at 10:22:00PM -0700, Yury Norov wrote:
> > 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.
> 
> Seems you forgot to update the commit message to explain the choise usage.

OK, I'll fold-in something like this:

The 'choice' and sudo config UNFORCE_NR_CPUS are used to ensure that 
auto-generated configs that try to enable as much options as possible,
like allmodconfig, don't enable FORCE_NR_CPUS.

Is that what you mean?