Re: [PATCH] Correct comment on efi_memmap_alloc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 14 Jun 2022 at 13:48, Liu Zixian <liuzixian4@xxxxxxxxxx> wrote:
>
> Returning zero means success now.
>
> Fixes: 1db91035d01a("efi: Add tracking for dynamically allocated memmaps")
> Signed-off-by: Liu Zixian <liuzixian4@xxxxxxxxxx>

Applied, thanks.

> ---
>  drivers/firmware/efi/memmap.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/efi/memmap.c b/drivers/firmware/efi/memmap.c
> index 4df55a55d..cf87dd7bb 100644
> --- a/drivers/firmware/efi/memmap.c
> +++ b/drivers/firmware/efi/memmap.c
> @@ -59,8 +59,7 @@ static void __init efi_memmap_free(void)
>   * Depending on whether mm_init() has already been invoked or not,
>   * either memblock or "normal" page allocation is used.
>   *
> - * Returns the physical address of the allocated memory map on
> - * success, zero on failure.
> + * Returns zero on success, a negative error code on failure.
>   */
>  int __init efi_memmap_alloc(unsigned int num_entries,
>                 struct efi_memory_map_data *data)
> --
> 2.33.0
>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux