(Note: tab whitespace damage)
So we get into this branch if CONFIG_NO_BOOTMEM is enabled but MAX_NUMNODES is
not defined? Doesnt look right.
Btw., and i said this before, i absolutely hate the CONFIG_NO_BOOTMEM naming
as well (a negative in the option), but it is was what expresses the 'this is
where we want to go' state better and thus CONFIG_NO_BOOTMEM removal will be a
straight removal instead of a removal of the inverse.
Thanks,
Ingo
--