From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"David S. Miller" <davem@davemloft.net>,
Dinh Nguyen <dinguyen@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Guo Ren <guoren@kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Max Filippov <jcmvbkbc@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Rich Felker <dalias@libc.org>,
Russell King <linux@armlinux.org.uk>,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Zi Yan <ziy@nvidia.com>,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org,
linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER
Date: Thu, 23 Mar 2023 13:17:25 +0300 [thread overview]
Message-ID: <20230323101725.2jmvpaqpzflr4mv2@box> (raw)
In-Reply-To: <20230323092156.2545741-1-rppt@kernel.org>
On Thu, Mar 23, 2023 at 11:21:42AM +0200, Mike Rapoport wrote:
> From: "Mike Rapoport (IBM)" <rppt@kernel.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@linux.intel.com>
--
Kiryl Shutsemau / Kirill A. Shutemov
prev parent reply other threads:[~2023-03-23 10:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 9:21 Mike Rapoport
2023-03-23 9:21 ` [PATCH 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-23 9:21 ` [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 10:15 ` Catalin Marinas
2023-03-23 10:37 ` Mike Rapoport
2023-03-23 11:57 ` Zi Yan
2023-03-23 13:46 ` kernel test robot
2023-03-23 17:11 ` kernel test robot
2023-03-23 9:21 ` [PATCH 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-23 10:30 ` Catalin Marinas
2023-03-23 9:21 ` [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` [PATCH 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` [PATCH 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-23 16:24 ` Geert Uytterhoeven
2023-03-23 9:21 ` [PATCH 07/14] nios2: " Mike Rapoport
2023-03-23 9:21 ` [PATCH 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` [PATCH 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-23 9:21 ` [PATCH 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` [PATCH 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-23 9:21 ` [PATCH 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` [PATCH 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-23 9:21 ` [PATCH 14/14] xtensa: " Mike Rapoport
2023-03-23 9:39 ` Max Filippov
2023-03-23 10:17 ` Kirill A. Shutemov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230323101725.2jmvpaqpzflr4mv2@box \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dalias@libc.org \
--cc=davem@davemloft.net \
--cc=dinguyen@kernel.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guoren@kernel.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rppt@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=will@kernel.org \
--cc=ysato@users.sourceforge.jp \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox