mem_map definition / declaration.

[Ralf Baechle]

mm/memory defines mem_map and max_mapnr only if !CONFIG_NEED_MULTIPLE_NODES.
<linux/mm.h> declares mem_map[] if !CONFIG_DISCONTIGMEM.  Shouldn't
both depend on !CONFIG_FLATMEM?  As things are now mem_map may be
declared but not defined for a non-NUMA sparsemem system which may make
tracking a remaining mem_map reference in the code a little harder.

  Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/