[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230323101725.2jmvpaqpzflr4mv2@box>
Date: Thu, 23 Mar 2023 13:17:25 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Mike Rapoport <rppt@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
"David S. Miller" <davem@...emloft.net>,
Dinh Nguyen <dinguyen@...nel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Guo Ren <guoren@...nel.org>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Max Filippov <jcmvbkbc@...il.com>,
Michael Ellerman <mpe@...erman.id.au>,
Rich Felker <dalias@...c.org>,
Russell King <linux@...linux.org.uk>,
Will Deacon <will@...nel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Zi Yan <ziy@...dia.com>, linux-arm-kernel@...ts.infradead.org,
linux-csky@...r.kernel.org, linux-ia64@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
linux-mm@...ck.org, linux-sh@...r.kernel.org,
linux-xtensa@...ux-xtensa.org, linuxppc-dev@...ts.ozlabs.org,
sparclinux@...r.kernel.org
Subject: Re: [PATCH 00/14] arch,mm: cleanup Kconfig entries for
ARCH_FORCE_MAX_ORDER
On Thu, Mar 23, 2023 at 11:21:42AM +0200, Mike Rapoport wrote:
> From: "Mike Rapoport (IBM)" <rppt@...nel.org>
>
> 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(-)
Acked-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists