[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHbLzkrk=P5tXutvX+W4acB5UWpmtY2w0V6B+aaR_QXjTbMZGg@mail.gmail.com>
Date: Thu, 20 May 2021 15:51:04 -0700
From: Yang Shi <shy828301@...il.com>
To: Mel Gorman <mgorman@...hsingularity.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...nel.org>,
David Hildenbrand <david@...hat.com>,
Vlastimil Babka <vbabka@...e.cz>,
Dan Streetman <ddstreet@...e.org>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/14] Clean W=1 build warnings for mm/
On Thu, May 20, 2021 at 1:48 AM Mel Gorman <mgorman@...hsingularity.net> wrote:
>
> This is a janitorial only. During development of a tool to catch build
> warnings early to avoid tripping the Intel lkp-robot, I noticed that mm/
> is not clean for W=1. This is generally harmless but there is no harm in
> cleaning it up. It disrupts git blame a little but on relatively obvious
> lines that are unlikely to be git blame targets.
>
> include/asm-generic/early_ioremap.h | 9 +++++++++
> include/linux/mmzone.h | 5 ++++-
> include/linux/swap.h | 6 +++++-
> mm/internal.h | 3 +--
> mm/mapping_dirty_helpers.c | 2 +-
> mm/memcontrol.c | 2 +-
> mm/memory_hotplug.c | 6 +++---
> mm/mmap_lock.c | 2 ++
> mm/page_alloc.c | 2 +-
> mm/vmalloc.c | 3 +++
> mm/vmscan.c | 2 +-
> mm/z3fold.c | 2 ++
> mm/zbud.c | 2 ++
> 13 files changed, 35 insertions(+), 11 deletions(-)
The whole series looks good to me. Reviewed-by: Yang Shi <shy828301@...il.com>
>
> --
> 2.26.2
>
Powered by blists - more mailing lists