Mike Rapoport 0075df288d microblaze: don't treat zero reserved memory regions as error ... Before commit 721f4a6526 ("mm/memblock: remove empty dummy entry") the check for non-zero of memblock.reserved.cnt in mmu_init() would always be true either because memblock.reserved.cnt is initialized to 1 or because there were memory reservations earlier. The removal of dummy empty entry in memblock caused this check to fail because now memblock.reserved.cnt is initialized to 0. Remove the check for non-zero of memblock.reserved.cnt because it's perfectly fine to have an empty memblock.reserved array that early in boot. Reported-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Mike Rapoport <rppt@kernel.org> Reviewed-by: Wei Yang <richard.weiyang@gmail.com> Tested-by: Guenter Roeck <linux@roeck-us.net> Link: https://lore.kernel.org/r/20240729053327.4091459-1-rppt@kernel.org Signed-off-by: Guenter Roeck <linux@roeck-us.net>		2024-08-25 15:26:30 -07:00
..
boot
configs	printk: Remove redundant CONFIG_BASE_FULL	2024-05-06 17:39:09 +02:00
include	arch: define CONFIG_PAGE_SIZE_*KB on all architectures	2024-03-06 19:29:09 +01:00
kernel	syscalls: mmap(): use unsigned offset type consistently	2024-06-25 15:57:38 +02:00
lib
mm	microblaze: don't treat zero reserved memory regions as error	2024-08-25 15:26:30 -07:00
pci
Kbuild
Kconfig	arch: define CONFIG_PAGE_SIZE_*KB on all architectures	2024-03-06 19:29:09 +01:00
Kconfig.debug
Kconfig.platform
Makefile