[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30bc19a0-4cd3-420e-92a9-7b3c97d6ad2c@redhat.com>
Date: Fri, 5 Jul 2024 11:03:03 +0200
From: David Hildenbrand <david@...hat.com>
To: Wei Yang <richard.weiyang@...il.com>, akpm@...ux-foundation.org,
masahiroy@...nel.org, nathan@...nel.org, nicolas@...sle.eu
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org, Mike Rapoport <rppt@...nel.org>
Subject: Re: [PATCH 1/3] mm: use zonelist_zone() to get zone
On 03.07.24 01:40, Wei Yang wrote:
> Instead of accessing zoneref->zone directly, use zonelist_zone() like
> other places for consistency.
>
> No functional change.
>
> Signed-off-by: Wei Yang <richard.weiyang@...il.com>
> CC: Mike Rapoport (IBM) <rppt@...nel.org>
> ---
> include/linux/mmzone.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index cb7f265c2b96..a34a74f5b113 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -1690,7 +1690,7 @@ static inline struct zoneref *first_zones_zonelist(struct zonelist *zonelist,
> zone = zonelist_zone(z))
>
> #define for_next_zone_zonelist_nodemask(zone, z, highidx, nodemask) \
> - for (zone = z->zone; \
> + for (zone = zonelist_zone(z); \
> zone; \
> z = next_zones_zonelist(++z, highidx, nodemask), \
> zone = zonelist_zone(z))
Should we do the same in movable_only_nodes as well to be consistent in
that file?
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists