Messages in this thread | | | From | Geert Uytterhoeven <> | Date | Wed, 19 Oct 2022 21:42:43 +0200 | Subject | Re: [PATCH] cpumask: limit visibility of FORCE_NR_CPUS |
| |
Hi Yuri,
On Wed, Oct 19, 2022 at 8:25 PM Yury Norov <yury.norov@gmail.com> wrote: > 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
sudo?
> 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?
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |