[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <146687646274.39261.14267596518720371009.stgit@dwillia2-desk3.amr.corp.intel.com>
Date: Sat, 25 Jun 2016 10:41:02 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: akpm@...ux-foundation.org
Cc: linux-mm@...ck.org, Eric Sandeen <sandeen@...hat.com>,
Jeff Moyer <jmoyer@...hat.com>, linux-kernel@...r.kernel.org,
linux-nvdimm@...ts.01.org
Subject: [PATCH 1/2] mm: CONFIG_ZONE_DEVICE stop depending on CONFIG_EXPERT
When it was first introduced CONFIG_ZONE_DEVICE depended on disabling
CONFIG_ZONE_DMA, a configuration choice reserved for "experts".
However, now that the ZONE_DMA conflict has been eliminated it no longer
makes sense to require CONFIG_EXPERT.
Reported-by: Eric Sandeen <sandeen@...hat.com>
Reported-by: Jeff Moyer <jmoyer@...hat.com>
Signed-off-by: Dan Williams <dan.j.williams@...el.com>
---
mm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/Kconfig b/mm/Kconfig
index 3e2daef3c946..d109a7a0c1c4 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -673,7 +673,7 @@ config IDLE_PAGE_TRACKING
See Documentation/vm/idle_page_tracking.txt for more details.
config ZONE_DEVICE
- bool "Device memory (pmem, etc...) hotplug support" if EXPERT
+ bool "Device memory (pmem, etc...) hotplug support"
depends on MEMORY_HOTPLUG
depends on MEMORY_HOTREMOVE
depends on SPARSEMEM_VMEMMAP
Powered by blists - more mailing lists