All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mm_init.c: Update obsolete comment in get_pfn_range_for_nid()
Date: Sun, 25 Jun 2023 08:06:12 +0300	[thread overview]
Message-ID: <20230625050612.GH52412@kernel.org> (raw)
In-Reply-To: <20230625033340.1054103-1-linmiaohe@huawei.com>

On Sun, Jun 25, 2023 at 11:33:40AM +0800, Miaohe Lin wrote:
> Since commit 633c0666b5a5 ("Memoryless nodes: drop one memoryless node boot
> warning"), the warning for a node with no available memory is removed.
> Update the corresponding comment.
> 
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>

Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>

> ---
>  mm/mm_init.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index 999723dee8cc..f90db54e2b21 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -1681,8 +1681,7 @@ static inline void alloc_node_mem_map(struct pglist_data *pgdat) { }
>   *
>   * It returns the start and end page frame of a node based on information
>   * provided by memblock_set_node(). If called for a node
> - * with no available memory, a warning is printed and the start and end
> - * PFNs will be 0.
> + * with no available memory, the start and end PFNs will be 0.
>   */
>  void __init get_pfn_range_for_nid(unsigned int nid,
>  			unsigned long *start_pfn, unsigned long *end_pfn)
> -- 
> 2.27.0
> 

-- 
Sincerely yours,
Mike.


      reply	other threads:[~2023-06-25  5:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  3:33 [PATCH] mm/mm_init.c: Update obsolete comment in get_pfn_range_for_nid() Miaohe Lin
2023-06-25  5:06 ` 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=20230625050612.GH52412@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.