* [merged mm-stable] sh-drop-ranges-for-definition-of-arch_force_max_order.patch removed from -mm tree
@ 2023-04-18 23:33 Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2023-04-18 23:33 UTC (permalink / raw)
To: mm-commits, ziy, ysato, will, mpe, linux, kirill.shutemov,
jcmvbkbc, guoren, glaubitz, geert, dinguyen, davem, dalias,
christophe.leroy, catalin.marinas, arnd, rppt, akpm
The quilt patch titled
Subject: sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER
has been removed from the -mm tree. Its filename was
sh-drop-ranges-for-definition-of-arch_force_max_order.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: "Mike Rapoport (IBM)" <rppt@kernel.org>
Subject: sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER
Date: Fri, 24 Mar 2023 08:22:31 +0300
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.
[rppt@kernel.org: untweak ARCH_FORCE_MAX_ORDER's `range']
Link: https://lkml.kernel.org/r/20230325060828.2662773-13-rppt@kernel.org
Link: https://lkml.kernel.org/r/20230324052233.2654090-13-rppt@kernel.org
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: Zi Yan <ziy@nvidia.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: David Miller <davem@davemloft.net>
Cc: Dinh Nguyen <dinguyen@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Guo Ren <guoren@kernel.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Max Filippov <jcmvbkbc@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Rich Felker <dalias@libc.org>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Will Deacon <will@kernel.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/sh/mm/Kconfig | 3 ---
1 file changed, 3 deletions(-)
--- a/arch/sh/mm/Kconfig~sh-drop-ranges-for-definition-of-arch_force_max_order
+++ a/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
_
Patches currently in -mm which might be from rppt@kernel.org are
sparc-reword-arch_force_max_order-prompt-and-help-text.patch
xtensa-reword-arch_force_max_order-prompt-and-help-text.patch
mm-move-free_area_empty-to-mm-internalh.patch
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-04-18 23:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-04-18 23:33 [merged mm-stable] sh-drop-ranges-for-definition-of-arch_force_max_order.patch removed from -mm tree Andrew Morton
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.