From: "Mike Rapoport (IBM)" <rppt@xxxxxxxxxx> Hi, Several architectures have ARCH_FORCE_MAX_ORDER in their Kconfig and they all have wrong and misleading prompt and help text for this option. Besides, some define insane limits for possible values of ARCH_FORCE_MAX_ORDER, some carefully define ranges only for a subset of possible configurations, some make this option configurable by users for no good reason. This set updates the prompt and help text everywhere and does its best to update actual definitions of ranges where applicable. Mike Rapoport (IBM) (14): arm: reword ARCH_FORCE_MAX_ORDER prompt and help text arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text csky: drop ARCH_FORCE_MAX_ORDER ia64: don't allow users to override ARCH_FORCE_MAX_ORDER m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER sh: reword ARCH_FORCE_MAX_ORDER prompt and help text sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text xtensa: reword ARCH_FORCE_MAX_ORDER prompt and help text arch/arm/Kconfig | 16 +++++++++------- arch/arm64/Kconfig | 27 ++++++++++++--------------- arch/csky/Kconfig | 4 ---- arch/ia64/Kconfig | 3 +-- arch/m68k/Kconfig.cpu | 16 +++++++++------- arch/nios2/Kconfig | 17 +++++++++-------- arch/powerpc/Kconfig | 22 +++++++++------------- arch/sh/mm/Kconfig | 19 +++++++++---------- arch/sparc/Kconfig | 16 +++++++++------- arch/xtensa/Kconfig | 16 +++++++++------- 10 files changed, 76 insertions(+), 80 deletions(-) base-commit: 51551d71edbc998fd8c8afa7312db3d270f5998e -- 2.35.1
