All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hoan Tran <Hoan@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-mm@kvack.org (open list:MEMORY MANAGEMENT),
	linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
	sparclinux@vger.kernel.org, x86@kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	lho@amperecomputing.com, mmorana@amperecomputing.com,
	Hoan Tran <Hoan@os.amperecomputing.com>
Subject: [PATCH v3 5/5] s390: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES
Date: Sat, 28 Mar 2020 11:31:22 -0700	[thread overview]
Message-ID: <1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com> (raw)
In-Reply-To: <1585420282-25630-1-git-send-email-Hoan@os.amperecomputing.com>

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.

Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
---
 arch/s390/Kconfig | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index bc88841..d86066e 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -449,14 +449,6 @@ config NR_CPUS
 config HOTPLUG_CPU
 	def_bool y
 
-# Some NUMA nodes have memory ranges that span
-# other nodes.	Even though a pfn is valid and
-# between a node's start and end pfns, it may not
-# reside on that node.	See memmap_init_zone()
-# for details. <- They meant memory holes!
-config NODES_SPAN_OTHER_NODES
-	def_bool NUMA
-
 config NUMA
 	bool "NUMA support"
 	depends on SCHED_TOPOLOGY
-- 
1.8.3.1


WARNING: multiple messages have this Message-ID (diff)
From: Hoan Tran <Hoan@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
	sparclinux@vger.kernel.org, x86@kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	lho@amperecomputing.com, mmorana@amperecomputing.com,
	Hoan Tran <Hoan@os.amperecomputing.com>
Subject: [PATCH v3 5/5] s390: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES
Date: Sat, 28 Mar 2020 11:31:22 -0700	[thread overview]
Message-ID: <1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com> (raw)
In-Reply-To: <1585420282-25630-1-git-send-email-Hoan@os.amperecomputing.com>

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.

Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
---
 arch/s390/Kconfig | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index bc88841..d86066e 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -449,14 +449,6 @@ config NR_CPUS
 config HOTPLUG_CPU
 	def_bool y
 
-# Some NUMA nodes have memory ranges that span
-# other nodes.	Even though a pfn is valid and
-# between a node's start and end pfns, it may not
-# reside on that node.	See memmap_init_zone()
-# for details. <- They meant memory holes!
-config NODES_SPAN_OTHER_NODES
-	def_bool NUMA
-
 config NUMA
 	bool "NUMA support"
 	depends on SCHED_TOPOLOGY
-- 
1.8.3.1

WARNING: multiple messages have this Message-ID (diff)
From: Hoan Tran <Hoan@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org, lho@amperecomputing.com,
	mmorana@amperecomputing.com, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	Hoan Tran <Hoan@os.amperecomputing.com>,
	sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] s390: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES
Date: Sat, 28 Mar 2020 18:31:22 +0000	[thread overview]
Message-ID: <1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com> (raw)
In-Reply-To: <1585420282-25630-1-git-send-email-Hoan@os.amperecomputing.com>

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.

Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
---
 arch/s390/Kconfig | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index bc88841..d86066e 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -449,14 +449,6 @@ config NR_CPUS
 config HOTPLUG_CPU
 	def_bool y
 
-# Some NUMA nodes have memory ranges that span
-# other nodes.	Even though a pfn is valid and
-# between a node's start and end pfns, it may not
-# reside on that node.	See memmap_init_zone()
-# for details. <- They meant memory holes!
-config NODES_SPAN_OTHER_NODES
-	def_bool NUMA
-
 config NUMA
 	bool "NUMA support"
 	depends on SCHED_TOPOLOGY
-- 
1.8.3.1

WARNING: multiple messages have this Message-ID (diff)
From: Hoan Tran <Hoan@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-mm@kvack.org (open list:MEMORY MANAGEMENT),
	linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
	sparclinux@vger.kernel.org, x86@kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org ,
	lho@amperecomputing.com, mmorana@amperecomputing.com,
	Hoan Tran <Hoan@os.amperecomputing.com>
Subject: [PATCH v3 5/5] s390: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES
Date: Sat, 28 Mar 2020 11:31:22 -0700	[thread overview]
Message-ID: <1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com> (raw)
In-Reply-To: <1585420282-25630-1-git-send-email-Hoan@os.amperecomputing.com>

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.

Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
---
 arch/s390/Kconfig | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index bc88841..d86066e 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -449,14 +449,6 @@ config NR_CPUS
 config HOTPLUG_CPU
 	def_bool y
 
-# Some NUMA nodes have memory ranges that span
-# other nodes.	Even though a pfn is valid and
-# between a node's start and end pfns, it may not
-# reside on that node.	See memmap_init_zone()
-# for details. <- They meant memory holes!
-config NODES_SPAN_OTHER_NODES
-	def_bool NUMA
-
 config NUMA
 	bool "NUMA support"
 	depends on SCHED_TOPOLOGY
-- 
1.8.3.1



WARNING: multiple messages have this Message-ID (diff)
From: Hoan Tran <Hoan@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org, lho@amperecomputing.com,
	mmorana@amperecomputing.com, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	Hoan Tran <Hoan@os.amperecomputing.com>,
	sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] s390: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES
Date: Sat, 28 Mar 2020 11:31:22 -0700	[thread overview]
Message-ID: <1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com> (raw)
In-Reply-To: <1585420282-25630-1-git-send-email-Hoan@os.amperecomputing.com>

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.

Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
---
 arch/s390/Kconfig | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index bc88841..d86066e 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -449,14 +449,6 @@ config NR_CPUS
 config HOTPLUG_CPU
 	def_bool y
 
-# Some NUMA nodes have memory ranges that span
-# other nodes.	Even though a pfn is valid and
-# between a node's start and end pfns, it may not
-# reside on that node.	See memmap_init_zone()
-# for details. <- They meant memory holes!
-config NODES_SPAN_OTHER_NODES
-	def_bool NUMA
-
 config NUMA
 	bool "NUMA support"
 	depends on SCHED_TOPOLOGY
-- 
1.8.3.1


WARNING: multiple messages have this Message-ID (diff)
From: Hoan Tran <Hoan@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org, lho@amperecomputing.com,
	mmorana@amperecomputing.com, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	Hoan Tran <Hoan@os.amperecomputing.com>,
	sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/5] s390: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES
Date: Sat, 28 Mar 2020 11:31:22 -0700	[thread overview]
Message-ID: <1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com> (raw)
In-Reply-To: <1585420282-25630-1-git-send-email-Hoan@os.amperecomputing.com>

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.

Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
---
 arch/s390/Kconfig | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index bc88841..d86066e 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -449,14 +449,6 @@ config NR_CPUS
 config HOTPLUG_CPU
 	def_bool y
 
-# Some NUMA nodes have memory ranges that span
-# other nodes.	Even though a pfn is valid and
-# between a node's start and end pfns, it may not
-# reside on that node.	See memmap_init_zone()
-# for details. <- They meant memory holes!
-config NODES_SPAN_OTHER_NODES
-	def_bool NUMA
-
 config NUMA
 	bool "NUMA support"
 	depends on SCHED_TOPOLOGY
-- 
1.8.3.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-03-28 18:32 UTC|newest]

Thread overview: 156+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 18:31 [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA Hoan Tran
2020-03-28 18:31 ` Hoan Tran
2020-03-28 18:31 ` Hoan Tran
2020-03-28 18:31 ` Hoan Tran
2020-03-28 18:31 ` Hoan Tran
2020-03-28 18:31 ` Hoan Tran
2020-03-28 18:31 ` [PATCH v3 1/5] " Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31 ` [PATCH v3 2/5] powerpc: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31 ` [PATCH v3 3/5] x86: " Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31 ` [PATCH v3 4/5] sparc: " Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31 ` Hoan Tran [this message]
2020-03-28 18:31   ` [PATCH v3 5/5] s390: " Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-28 18:31   ` Hoan Tran
2020-03-29  0:19 ` [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA Baoquan He
2020-03-29  0:19   ` Baoquan He
2020-03-29  0:19   ` Baoquan He
2020-03-29  0:19   ` Baoquan He
2020-03-30  7:44   ` Michal Hocko
2020-03-30  7:44     ` Michal Hocko
2020-03-30  7:44     ` Michal Hocko
2020-03-30  7:44     ` Michal Hocko
2020-03-30  8:04     ` Baoquan He
2020-03-30  8:04       ` Baoquan He
2020-03-30  8:04       ` Baoquan He
2020-03-30  8:04       ` Baoquan He
2020-03-30  7:42 ` Michal Hocko
2020-03-30  7:42   ` Michal Hocko
2020-03-30  7:42   ` Michal Hocko
2020-03-30  7:42   ` Michal Hocko
2020-03-30  8:16   ` Baoquan He
2020-03-30  8:16     ` Baoquan He
2020-03-30  8:16     ` Baoquan He
2020-03-30  8:16     ` Baoquan He
2020-03-30  8:28     ` Baoquan He
2020-03-30  8:28       ` Baoquan He
2020-03-30  8:28       ` Baoquan He
2020-03-30  8:28       ` Baoquan He
2020-03-30  9:21   ` Mike Rapoport
2020-03-30  9:21     ` Mike Rapoport
2020-03-30  9:21     ` Mike Rapoport
2020-03-30  9:21     ` Mike Rapoport
2020-03-30  9:58     ` Michal Hocko
2020-03-30  9:58       ` Michal Hocko
2020-03-30  9:58       ` Michal Hocko
2020-03-30  9:58       ` Michal Hocko
2020-03-30 10:26       ` Mike Rapoport
2020-03-30 10:26         ` Mike Rapoport
2020-03-30 10:26         ` Mike Rapoport
2020-03-30 10:26         ` Mike Rapoport
2020-03-30 10:43         ` Baoquan He
2020-03-30 10:43           ` Baoquan He
2020-03-30 10:43           ` Baoquan He
2020-03-30 10:43           ` Baoquan He
2020-03-31 21:56       ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Mike Rapoport
2020-03-31 21:56         ` Mike Rapoport
2020-03-31 21:56         ` Mike Rapoport
2020-03-31 21:56         ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODE Mike Rapoport
2020-04-01  5:42         ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Baoquan He
2020-04-01  5:42           ` Baoquan He
2020-04-01  5:42           ` Baoquan He
2020-04-01  5:42           ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_ Baoquan He
2020-04-01  7:51           ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Mike Rapoport
2020-04-01  7:51             ` Mike Rapoport
2020-04-01  7:51             ` Mike Rapoport
2020-04-01  7:51             ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_ Mike Rapoport
2020-04-02  8:01             ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Michal Hocko
2020-04-02  8:01               ` Michal Hocko
2020-04-02  8:01               ` Michal Hocko
2020-04-02  8:01               ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_ Michal Hocko
2020-04-09 14:41               ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Baoquan He
2020-04-09 14:41                 ` Baoquan He
2020-04-09 14:41                 ` Baoquan He
2020-04-09 14:41                 ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_ Baoquan He
2020-04-09 15:33                 ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Michal Hocko
2020-04-09 15:33                   ` Michal Hocko
2020-04-09 15:33                   ` Michal Hocko
2020-04-09 15:33                   ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_ Michal Hocko
2020-04-10  6:46                   ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA) Baoquan He
2020-04-10  6:46                     ` Baoquan He
2020-04-10  6:46                     ` Baoquan He
2020-04-10  6:46                     ` [PATCH RFC] mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP (was: Re: [PATCH v3 0/5] mm: Enable CONFIG_ Baoquan He
2020-03-30  9:26   ` [PATCH v3 0/5] mm: Enable CONFIG_NODES_SPAN_OTHER_NODES by default for NUMA Baoquan He
2020-03-30  9:26     ` Baoquan He
2020-03-30  9:26     ` Baoquan He
2020-03-30  9:26     ` Baoquan He
2020-03-30 17:51   ` Mike Rapoport
2020-03-30 17:51     ` Mike Rapoport
2020-03-30 17:51     ` Mike Rapoport
2020-03-30 17:51     ` Mike Rapoport
2020-03-30 18:23     ` Michal Hocko
2020-03-30 18:23       ` Michal Hocko
2020-03-30 18:23       ` Michal Hocko
2020-03-30 18:23       ` Michal Hocko
2020-03-31  8:14       ` Mike Rapoport
2020-03-31  8:14         ` Mike Rapoport
2020-03-31  8:14         ` Mike Rapoport
2020-03-31  8:14         ` Mike Rapoport
2020-03-31  8:55         ` Michal Hocko
2020-03-31  8:55           ` Michal Hocko
2020-03-31  8:55           ` Michal Hocko
2020-03-31  8:55           ` Michal Hocko
2020-03-31 14:03           ` Baoquan He
2020-03-31 14:03             ` Baoquan He
2020-03-31 14:03             ` Baoquan He
2020-03-31 14:03             ` Baoquan He
2020-03-31 14:21             ` Michal Hocko
2020-03-31 14:21               ` Michal Hocko
2020-03-31 14:21               ` Michal Hocko
2020-03-31 14:21               ` Michal Hocko
2020-03-31 14:31               ` Baoquan He
2020-03-31 14:31                 ` Baoquan He
2020-03-31 14:31                 ` Baoquan He
2020-03-31 14:31                 ` Baoquan He
2020-04-03  4:46                 ` Hoan Tran
2020-04-03  4:46                   ` Hoan Tran
2020-04-03  4:46                   ` Hoan Tran
2020-04-03  4:46                   ` Hoan Tran
2020-04-03  7:09                   ` Baoquan He
2020-04-03  7:09                     ` Baoquan He
2020-04-03  7:09                     ` Baoquan He
2020-04-03  7:09                     ` Baoquan He
2020-04-03 16:36                     ` Hoan Tran
2020-04-03 16:36                       ` Hoan Tran
2020-04-03 16:36                       ` Hoan Tran
2020-04-03 16:36                       ` Hoan Tran
2020-04-09 16:27               ` Mike Rapoport
2020-04-09 16:27                 ` Mike Rapoport
2020-04-09 16:27                 ` Mike Rapoport
2020-04-09 16:27                 ` Mike Rapoport
2020-04-10  6:50                 ` Baoquan He
2020-04-10  6:50                   ` Baoquan He
2020-04-10  6:50                   ` Baoquan He
2020-04-10  6:50                   ` Baoquan He

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=1585420282-25630-6-git-send-email-Hoan@os.amperecomputing.com \
    --to=hoan@os.amperecomputing.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=borntraeger@de.ibm.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=davem@davemloft.net \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=lho@amperecomputing.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=mmorana@amperecomputing.com \
    --cc=mpe@ellerman.id.au \
    --cc=osalvador@suse.de \
    --cc=paulus@samba.org \
    --cc=pavel.tatashin@microsoft.com \
    --cc=rppt@linux.ibm.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vbabka@suse.cz \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.org \
    /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.