]> Git Repo - linux.git/commit
arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER
authorMike Rapoport (IBM) <[email protected]>
Fri, 24 Mar 2023 05:22:21 +0000 (08:22 +0300)
committerAndrew Morton <[email protected]>
Tue, 18 Apr 2023 23:29:44 +0000 (16:29 -0700)
commit34affcd7577a232803f729d1870ba475f294e4ea
tree5adb54d8fd2a99be3388fd8d3c42ded8080e62d5
parent8c907785b8cc6dff2b9dda52e499715b0c64f377
arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER

It is not a good idea to change fundamental parameters of core memory
management.  Having predefined ranges suggests that the values within
those ranges are sensible, but one has to *really* understand implications
of changing MAX_ORDER before actually amending it and ranges don't help
here.

Drop ranges in definition of ARCH_FORCE_MAX_ORDER and make its prompt
visible only if EXPERT=y

Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Mike Rapoport (IBM) <[email protected]>
Reviewed-by: Zi Yan <[email protected]>
Reviewed-by: Kefeng Wang <[email protected]>
Cc: Arnd Bergmann <[email protected]>
Cc: Catalin Marinas <[email protected]>
Cc: Christophe Leroy <[email protected]>
Cc: David Miller <[email protected]>
Cc: Dinh Nguyen <[email protected]>
Cc: Geert Uytterhoeven <[email protected]>
Cc: Guo Ren <[email protected]>
Cc: John Paul Adrian Glaubitz <[email protected]>
Cc: Kirill A. Shutemov <[email protected]>
Cc: Max Filippov <[email protected]>
Cc: Michael Ellerman <[email protected]>
Cc: Rich Felker <[email protected]>
Cc: "Russell King (Oracle)" <[email protected]>
Cc: Will Deacon <[email protected]>
Cc: Yoshinori Sato <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
arch/arm64/Kconfig
This page took 0.043947 seconds and 4 git commands to generate.