Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 25 May 2021 15:25:24 +0100
From:   Mel Gorman <mgorman@techsingularity.net>
To:     Vlastimil Babka <vbabka@suse.cz>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Michal Hocko <mhocko@kernel.org>,
        David Hildenbrand <david@redhat.com>,
        Dan Streetman <ddstreet@ieee.org>,
        Yang Shi <shy828301@gmail.com>, Linux-MM <linux-mm@kvack.org>,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/14] Clean W=1 build warnings for mm/
Message-ID: <20210525142524.GU30378@techsingularity.net>
References: <20210520084809.8576-1-mgorman@techsingularity.net>
 <aad3f04f-850a-b134-d0a7-b24af9721ddb@suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <aad3f04f-850a-b134-d0a7-b24af9721ddb@suse.cz>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Tue, May 25, 2021 at 01:48:26PM +0200, Vlastimil Babka wrote:
> On 5/20/21 10:47 AM, Mel Gorman 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(-)
> 
> Thanks, looks good.
> 
> patch 3/14 subject looks like it should read just "mm/page_alloc: Make
> should_fail_alloc_page a static function"
> 

Yes it should. Andrew, do you mind fixing it directly instead of
resending the entire series?

> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> 

Thanks!

-- 
Mel Gorman
SUSE Labs