From: "Mike Rapoport (IBM)" <rppt@xxxxxxxxxx> The default value of ARCH_FORCE_MAX_ORDER matches the generic default defined in the MM code, the architecture does not support huge pages, so there is no need to keep ARCH_FORCE_MAX_ORDER option available. Drop it. Acked-by: Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx> Reviewed-by: Zi Yan <ziy@xxxxxxxxxx> Signed-off-by: Mike Rapoport (IBM) <rppt@xxxxxxxxxx> --- arch/csky/Kconfig | 4 ---- 1 file changed, 4 deletions(-) diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig index c694fac43bed..00379a843c37 100644 --- a/arch/csky/Kconfig +++ b/arch/csky/Kconfig @@ -332,10 +332,6 @@ config HIGHMEM select KMAP_LOCAL default y -config ARCH_FORCE_MAX_ORDER - int "Maximum zone order" - default "10" - config DRAM_BASE hex "DRAM start addr (the same with memory-section in dts)" default 0x0 -- 2.35.1
