Atish Patra c026844c61 RISC-V: Define MAXPHYSMEM_1GB only for RV32 ... commit de5f4b8f634beacf667e6eff334522601dd03b59 upstream. MAXPHYSMEM_1GB option was added for RV32 because RV32 only supports 1GB of maximum physical memory. This lead to few compilation errors reported by kernel test robot which created the following configuration combination which are not useful but can be configured. 1. MAXPHYSMEM_1GB & RV64 2, MAXPHYSMEM_2GB & RV32 Fix this by restricting MAXPHYSMEM_1GB for RV32 and MAXPHYSMEM_2GB only for RV64. Fixes: e557793799c5 ("RISC-V: Fix maximum allowed phsyical memory for RV32") Cc: stable@vger.kernel.org Reported-by: Randy Dunlap <rdunlap@infradead.org> Acked-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Atish Patra <atish.patra@wdc.com> Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2021-02-10 09:29:17 +01:00
..
boot	dts: phy: add GPIO number and active state used for phy reset	2021-01-27 11:55:01 +01:00
configs	riscv: defconfig: enable gpio support for HiFive Unleashed	2021-01-27 11:55:01 +01:00
include	riscv: Fixup CONFIG_GENERIC_TIME_VSYSCALL	2021-01-19 18:27:20 +01:00
kernel	riscv: cacheinfo: Fix using smp_processor_id() in preemptible	2021-01-27 11:55:00 +01:00
lib	riscv: use memcpy based uaccess for nommu again	2020-10-04 10:27:07 -07:00
mm	RISC-V: Set current memblock limit	2021-01-27 11:55:04 +01:00
net	treewide: Use fallthrough pseudo-keyword	2020-08-23 17:36:59 -05:00
Kbuild	riscv: Allow device trees to be built into the kernel	2020-05-18 11:38:05 -07:00
Kconfig	RISC-V: Define MAXPHYSMEM_1GB only for RV32	2021-02-10 09:29:17 +01:00
Kconfig.debug	RISC-V: Remove EARLY_PRINTK support	2018-12-17 10:23:46 -08:00
Kconfig.socs	RISC-V: Remove CLINT related code from timer and arch	2020-08-20 10:58:13 -07:00
Makefile	Kbuild updates for v5.10	2020-10-22 13:13:57 -07:00