From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mike Rapoport <rppt@kernel.org>, 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: [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER
Date: Thu, 23 Mar 2023 11:21:46 +0200 [thread overview]
Message-ID: <20230323092156.2545741-5-rppt@kernel.org> (raw)
In-Reply-To: <20230323092156.2545741-1-rppt@kernel.org>
From: "Mike Rapoport (IBM)" <rppt@kernel.org>
The default value of ARCH_FORCE_MAX_ORDER matches the generic default
defined in the MM code, the architecture does not support huge pages, so
there is no need to keep ARCH_FORCE_MAX_ORDER option available.
Drop it.
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
---
arch/csky/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig
index c694fac43bed..00379a843c37 100644
--- a/arch/csky/Kconfig
+++ b/arch/csky/Kconfig
@@ -332,10 +332,6 @@ config HIGHMEM
select KMAP_LOCAL
default y
-config ARCH_FORCE_MAX_ORDER
- int "Maximum zone order"
- default "10"
-
config DRAM_BASE
hex "DRAM start addr (the same with memory-section in dts)"
default 0x0
--
2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mike Rapoport <rppt@kernel.org>, 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: [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER
Date: Thu, 23 Mar 2023 11:21:46 +0200 [thread overview]
Message-ID: <20230323092156.2545741-5-rppt@kernel.org> (raw)
In-Reply-To: <20230323092156.2545741-1-rppt@kernel.org>
From: "Mike Rapoport (IBM)" <rppt@kernel.org>
The default value of ARCH_FORCE_MAX_ORDER matches the generic default
defined in the MM code, the architecture does not support huge pages, so
there is no need to keep ARCH_FORCE_MAX_ORDER option available.
Drop it.
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
---
arch/csky/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig
index c694fac43bed..00379a843c37 100644
--- a/arch/csky/Kconfig
+++ b/arch/csky/Kconfig
@@ -332,10 +332,6 @@ config HIGHMEM
select KMAP_LOCAL
default y
-config ARCH_FORCE_MAX_ORDER
- int "Maximum zone order"
- default "10"
-
config DRAM_BASE
hex "DRAM start addr (the same with memory-section in dts)"
default 0x0
--
2.35.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Max Filippov <jcmvbkbc@gmail.com>, Guo Ren <guoren@kernel.org>,
linux-csky@vger.kernel.org, sparclinux@vger.kernel.org,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Russell King <linux@armlinux.org.uk>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Zi Yan <ziy@nvidia.com>,
linux-xtensa@linux-xtensa.org, Arnd Bergmann <arnd@arndb.de>,
linux-m68k@lists.linux-m68k.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Dinh Nguyen <dinguyen@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
Mike Rapoport <rppt@kernel.org>
Subject: [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER
Date: Thu, 23 Mar 2023 11:21:46 +0200 [thread overview]
Message-ID: <20230323092156.2545741-5-rppt@kernel.org> (raw)
In-Reply-To: <20230323092156.2545741-1-rppt@kernel.org>
From: "Mike Rapoport (IBM)" <rppt@kernel.org>
The default value of ARCH_FORCE_MAX_ORDER matches the generic default
defined in the MM code, the architecture does not support huge pages, so
there is no need to keep ARCH_FORCE_MAX_ORDER option available.
Drop it.
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
---
arch/csky/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig
index c694fac43bed..00379a843c37 100644
--- a/arch/csky/Kconfig
+++ b/arch/csky/Kconfig
@@ -332,10 +332,6 @@ config HIGHMEM
select KMAP_LOCAL
default y
-config ARCH_FORCE_MAX_ORDER
- int "Maximum zone order"
- default "10"
-
config DRAM_BASE
hex "DRAM start addr (the same with memory-section in dts)"
default 0x0
--
2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mike Rapoport <rppt@kernel.org>, 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: [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER
Date: Thu, 23 Mar 2023 09:21:46 +0000 [thread overview]
Message-ID: <20230323092156.2545741-5-rppt@kernel.org> (raw)
In-Reply-To: <20230323092156.2545741-1-rppt@kernel.org>
From: "Mike Rapoport (IBM)" <rppt@kernel.org>
The default value of ARCH_FORCE_MAX_ORDER matches the generic default
defined in the MM code, the architecture does not support huge pages, so
there is no need to keep ARCH_FORCE_MAX_ORDER option available.
Drop it.
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
---
arch/csky/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/csky/Kconfig b/arch/csky/Kconfig
index c694fac43bed..00379a843c37 100644
--- a/arch/csky/Kconfig
+++ b/arch/csky/Kconfig
@@ -332,10 +332,6 @@ config HIGHMEM
select KMAP_LOCAL
default y
-config ARCH_FORCE_MAX_ORDER
- int "Maximum zone order"
- default "10"
-
config DRAM_BASE
hex "DRAM start addr (the same with memory-section in dts)"
default 0x0
--
2.35.1
next prev parent reply other threads:[~2023-03-23 9:23 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 9:21 [PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 10:15 ` Catalin Marinas
2023-03-23 10:15 ` Catalin Marinas
2023-03-23 10:15 ` Catalin Marinas
2023-03-23 10:37 ` Mike Rapoport
2023-03-23 10:37 ` Mike Rapoport
2023-03-23 10:37 ` Mike Rapoport
2023-03-23 10:37 ` Mike Rapoport
2023-03-23 11:57 ` Zi Yan
2023-03-23 11:57 ` Zi Yan
2023-03-23 11:57 ` Zi Yan
2023-03-23 11:57 ` Zi Yan
2023-03-23 13:46 ` kernel test robot
2023-03-23 13:46 ` kernel test robot
2023-03-23 13:46 ` kernel test robot
2023-03-23 13:46 ` kernel test robot
2023-03-23 17:11 ` kernel test robot
2023-03-23 17:11 ` kernel test robot
2023-03-23 17:11 ` 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 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 10:30 ` Catalin Marinas
2023-03-23 10:30 ` Catalin Marinas
2023-03-23 10:30 ` Catalin Marinas
2023-03-23 9:21 ` Mike Rapoport [this message]
2023-03-23 9:21 ` [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 16:24 ` Geert Uytterhoeven
2023-03-23 16:24 ` Geert Uytterhoeven
2023-03-23 16:24 ` Geert Uytterhoeven
2023-03-23 16:24 ` Geert Uytterhoeven
2023-03-23 9:21 ` [PATCH 07/14] nios2: " Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` 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 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` [PATCH 14/14] xtensa: " Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:21 ` Mike Rapoport
2023-03-23 9:39 ` Max Filippov
2023-03-23 9:39 ` Max Filippov
2023-03-23 9:39 ` Max Filippov
2023-03-23 9:39 ` Max Filippov
2023-03-23 10:17 ` [PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER Kirill A. Shutemov
2023-03-23 10:17 ` Kirill A. Shutemov
2023-03-23 10:17 ` Kirill A. Shutemov
2023-03-23 10:17 ` Kirill A. Shutemov
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=20230323092156.2545741-5-rppt@kernel.org \
--to=rppt@kernel.org \
--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=kirill.shutemov@linux.intel.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=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 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.