Hi, It seems that this series is stale for more than one month with maintainers comments given for [1][2] and some discussions between maintainer and author for [3]. So this email is a gentle reminder for the author about this series (no hurries and pressure though, please take your time :) ). Thanks!
Kind regards, Henry [1] https://patchwork.kernel.org/project/xen-devel/patch/Yl7X3mAJhR5ENSpl@itl-email/ [2] https://patchwork.kernel.org/project/xen-devel/patch/Yl7X/dT39vvhZmho@itl-email/ [3] https://patchwork.kernel.org/project/xen-devel/patch/Yl7aC2a+TtOaFtqZ@itl-email/ > -----Original Message----- > On 19.04.2022 17:40, Demi Marie Obenour wrote: > > @@ -1056,19 +1091,19 @@ static void __init efi_exit_boot(EFI_HANDLE > ImageHandle, EFI_SYSTEM_TABLE *Syste > > EFI_STATUS status; > > UINTN info_size = 0, map_key; > > bool retry; > > -#ifdef CONFIG_EFI_SET_VIRTUAL_ADDRESS_MAP > > unsigned int i; > > -#endif > > > > efi_bs->GetMemoryMap(&info_size, NULL, &map_key, > > &efi_mdesc_size, &mdesc_ver); > > - info_size += 8 * efi_mdesc_size; > > + info_size += 8 * (efi_mdesc_size + 1); > > efi_memmap = efi_arch_allocate_mmap_buffer(info_size); > > if ( !efi_memmap ) > > blexit(L"Unable to allocate memory for EFI memory map"); > > > > for ( retry = false; ; retry = true ) > > { > > + esrt_desc = (const EFI_MEMORY_DESCRIPTOR > *)EFI_INVALID_TABLE_ADDR; > > Sorry, one more question here: Why is NULL not good enough? > > Jan >
