[PATCH v3 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER
From: Mike Rapoport <rppt@kernel.org>
Date: 2023-03-25 06:11:30
Also in:
linux-arm-kernel, linux-m68k, linux-mm, linux-sh, lkml, sparclinux
Subsystem:
superh, the rest · Maintainers:
Yoshinori Sato, Rich Felker, John Paul Adrian Glaubitz, Linus Torvalds
From: "Mike Rapoport (IBM)" <rppt@kernel.org> sh defines insane ranges for ARCH_FORCE_MAX_ORDER allowing MAX_ORDER up to 63, which implies maximal contiguous allocation size of 2^63 pages. Drop bogus definitions of ranges for ARCH_FORCE_MAX_ORDER and leave it a simple integer with sensible defaults. Users that *really* need to change the value of ARCH_FORCE_MAX_ORDER will be able to do so but they won't be mislead by the bogus ranges. Acked-by: Kirill A. Shutemov <redacted> Reviewed-by: Zi Yan <ziy@nvidia.com> Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org> --- arch/sh/mm/Kconfig | 3 --- 1 file changed, 3 deletions(-)
diff --git a/arch/sh/mm/Kconfig b/arch/sh/mm/Kconfig
index 238b2772751e..511c17aede4a 100644
--- a/arch/sh/mm/Kconfig
+++ b/arch/sh/mm/Kconfig@@ -20,11 +20,8 @@ config PAGE_OFFSET config ARCH_FORCE_MAX_ORDER int "Order of maximal physically contiguous allocations" - range 8 63 if PAGE_SIZE_16KB default "8" if PAGE_SIZE_16KB - range 6 63 if PAGE_SIZE_64KB default "6" if PAGE_SIZE_64KB - range 10 63 default "13" if !MMU default "10" help
--
2.35.1