mm/cma: make MAX_CMA_AREAS = CONFIG_CMA_AREAS
authorAnshuman Khandual <anshuman.khandual@arm.com>
Mon, 5 Feb 2024 05:19:29 +0000 (10:49 +0530)
committerAndrew Morton <akpm@linux-foundation.org>
Thu, 22 Feb 2024 18:24:53 +0000 (10:24 -0800)
commit73307523c9bbc4e3b35f0058cdbc15e32bd83c52
tree98526f63a92ae83e4411e00068c5d02afd2a45e6
parentfe58582c0e362d5e52b97985142b0dcef920b745
mm/cma: make MAX_CMA_AREAS = CONFIG_CMA_AREAS

There is no real difference between the global area, and other
additionally configured CMA areas via CONFIG_CMA_AREAS that always
defaults without user input.  This makes MAX_CMA_AREAS same as
CONFIG_CMA_AREAS, also incrementing its default values, thus maintaining
current default for MAX_CMA_AREAS both for UMA and NUMA systems.

Link: https://lkml.kernel.org/r/20240205051929.298559-1-anshuman.khandual@arm.com
Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
include/linux/cma.h
mm/Kconfig