From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D198C46467 for ; Wed, 4 Jan 2023 10:32:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234672AbjADKcm (ORCPT ); Wed, 4 Jan 2023 05:32:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50506 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233383AbjADKcf (ORCPT ); Wed, 4 Jan 2023 05:32:35 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E8E9B1C93A for ; Wed, 4 Jan 2023 02:32:34 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 874E5616A0 for ; Wed, 4 Jan 2023 10:32:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9D2C8C433D2; Wed, 4 Jan 2023 10:32:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1672828353; bh=GkTdvslnrFVBa2cyBAB43WHO7wxBxOn/8ycIzVEF8Gc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WF1R2MPVg4cO38YS1OVSyYHzd705Ua+IW7gNEIeuwmpvMSRzWc+Md3ZjIRrjlxPGQ dhCXaOT21pgMz/Lmx9+LlB+T7XAI6QCPLImfFO/RgQU+CVnqRvyv8Svfc32cfCKm8l rIHPpibjJBtK9UtBhYNXd9X74L8r7csGZd1DXOYK9xFQILQO0dIKbpxrbl+by3m0xf X9y8bfFIyQDUY0purZazeuVj9UMNfQFKiU/ugk6jEubWF2O3q/TN6CllewABPh8hOi 3rXS5nVFNNbVPl0TWrnXkGgE6YxOxiT1bFnLKhuS5TvETHMlTZllzuw2+YOgyjhNUx SD4byWRxwrNBw== Date: Wed, 4 Jan 2023 12:32:19 +0200 From: Mike Rapoport To: Miaoqian Lin Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] memblock: Fix doc for memblock_phys_free Message-ID: References: <20221216100304.688209-1-linmq006@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221216100304.688209-1-linmq006@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > --- > 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.