MIPS: Octeon: drop dependency on CONFIG_HOLES_IN_ZONE

CAVIUM_OCTEON_SOC configuration selects HOLES_IN_ZONE option to cope with
memory crashes that were happening in 2011.

This option effectively aliases pfn_valid_within() to pfn_valid() when
enabled and hardwires it to 1 when disabled. The check for
pfn_valid_within() is only relevant in case the memory map may have holes
or undefined struct page instances inside MAX_ORDER chunks.

Since 2011 memory management initialization in general and memory map
initialization particularly became much more robust so the check for
pfn_valid_within() is not required on Octeon even despite its, hmm, unusual
memory setup.

Remove the selection of HOLES_IN_ZONE by CAVIUM_OCTEON_SOC and drop the
HOLES_IN_ZONE configuration option entirely as Octeon was the only MIPS
platform to use it.

Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index ed51970..baa4ea9 100644 (file)
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -996,7 +996,6 @@ config CAVIUM_OCTEON_SOC
        select HAVE_PLAT_FW_INIT_CMDLINE
        select HAVE_PLAT_MEMCPY
        select ZONE_DMA32
-       select HOLES_IN_ZONE
        select GPIOLIB
        select USE_OF
        select ARCH_SPARSEMEM_ENABLE
@@ -1233,9 +1232,6 @@ config HAVE_PLAT_MEMCPY
 config ISA_DMA_API
        bool
 
-config HOLES_IN_ZONE
-       bool
-
 config SYS_SUPPORTS_RELOCATABLE
        bool
        help