Atish Patra de5f4b8f63 RISC-V: Define MAXPHYSMEM_1GB only for RV32 ... 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: e557793799 ("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>		2021-02-02 18:36:42 -08:00
..
boot	dts: phy: add GPIO number and active state used for phy reset	2021-01-13 20:59:16 -08:00
configs	riscv: defconfig: enable gpio support for HiFive Unleashed	2021-01-13 20:59:46 -08:00
include	riscv: Align on L1_CACHE_BYTES when STRICT_KERNEL_RWX	2021-02-02 18:36:29 -08:00
kernel	RISC-V: Fix .init section permission update	2021-02-02 18:35:42 -08:00
lib
mm	riscv: Fixup pfn_valid error with wrong max_mapnr	2021-01-22 20:18:03 -08:00
net
Kbuild
Kconfig	RISC-V: Define MAXPHYSMEM_1GB only for RV32	2021-02-02 18:36:42 -08:00
Kconfig.debug
Kconfig.socs	clk: sifive: Use common name for prci configuration	2020-12-16 12:22:59 -08:00
Makefile