Re: m68k: default value for MEMORY_RESERVE?
From: Geert Uytterhoeven
Date: Tue Sep 28 2021 - 03:20:29 EST
On Mon, Sep 27, 2021 at 11:26 PM Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote:
> Would it be safe (or unsafe) to add a default value for MEMORY_RESERVE?
No idea ;-)
> As it is, kconfig can generate a randconfig with
> "CONFIG_MEMORY_RESERVE=" (no value) since it has no default.
> Then a following 'make all' finds an invalid symbol value and restarts
> the config:
> .config:214:warning: symbol value '' invalid for MEMORY_RESERVE
> * Restart config...
> Memory reservation (MiB) (MEMORY_RESERVE)  (NEW)
> That's OK until I try to script/automate randconfig builds.
> Can we do anything about this or should I just add it to my
Looking at its sole user, I guess "default 0" would be fine.
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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