public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memblock: Fix doc for memblock_phys_free
Date: Wed, 4 Jan 2023 12:32:19 +0200	[thread overview]
Message-ID: <Y7VVs//O0OE3Eebv@kernel.org> (raw)
In-Reply-To: <20221216100304.688209-1-linmq006@gmail.com>

On Fri, Dec 16, 2022 at 02:03:03PM +0400, Miaoqian Lin wrote:
> memblock_phys_free() is the counterpart to memblock_phys_alloc.
> Change memblock_alloc_xx() with memblock_phys_alloc_xx() to keep
> a consistency.
> 
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
>  mm/memblock.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 511d4783dcf1..d036c7861310 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -836,7 +836,7 @@ void __init_memblock memblock_free(void *ptr, size_t size)
>   * @base: phys starting address of the  boot memory block
>   * @size: size of the boot memory block in bytes
>   *
> - * Free boot memory block previously allocated by memblock_alloc_xx() API.
> + * Free boot memory block previously allocated by memblock_phys_alloc_xx() API.
>   * The freeing memory will not be released to the buddy allocator.
>   */
>  int __init_memblock memblock_phys_free(phys_addr_t base, phys_addr_t size)
> -- 
> 2.25.1

Applied, thanks! 

-- 
Sincerely yours,
Mike.

      reply	other threads:[~2023-01-04 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 10:03 [PATCH] memblock: Fix doc for memblock_phys_free Miaoqian Lin
2023-01-04 10:32 ` Mike Rapoport [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y7VVs//O0OE3Eebv@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linmq006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox