All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/4] mm/page_alloc: fix a typo in comment about GFP flag
Date: Sun, 23 Jun 2024 10:50:52 +0300	[thread overview]
Message-ID: <ZnfT3FXgXz0JdUwi@kernel.org> (raw)
In-Reply-To: <20240619010612.20740-3-richard.weiyang@gmail.com>

On Wed, Jun 19, 2024 at 01:06:11AM +0000, Wei Yang wrote:
> The GFP flags used to choose the zonelist is __GFP_THISNODE.
> 
> Let's change it to what exactly it should be.
> 
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>

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

> ---
>  mm/page_alloc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index f3ba1ede142d..594176449890 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5209,7 +5209,7 @@ static void build_zonelists_in_node_order(pg_data_t *pgdat, int *node_order,
>  }
>  
>  /*
> - * Build gfp_thisnode zonelists
> + * Build __GFP_THISNODE zonelists
>   */
>  static void build_thisnode_zonelists(pg_data_t *pgdat)
>  {
> -- 
> 2.34.1
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2024-06-23  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  1:06 [PATCH 1/4] mm/sparse: nr_pages won't be 0 Wei Yang
2024-06-19  1:06 ` [PATCH 2/4] mm/mm_init.c: move build check on MAX_ZONELISTS out of ifdef Wei Yang
2024-06-23  7:48   ` Mike Rapoport
2024-06-19  1:06 ` [PATCH 3/4] mm/page_alloc: fix a typo in comment about GFP flag Wei Yang
2024-06-23  7:50   ` Mike Rapoport [this message]
2024-06-19  1:06 ` [PATCH 4/4] mm/page_alloc: reword the comment of buddy_merge_likely() Wei Yang

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=ZnfT3FXgXz0JdUwi@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=richard.weiyang@gmail.com \
    /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.