[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1564641003.25219.7.camel@mtkswgap22>
Date: Thu, 1 Aug 2019 14:30:03 +0800
From: Miles Chen <miles.chen@...iatek.com>
To: Michal Hocko <mhocko@...nel.org>
CC: Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Qian Cai <cai@....pw>
Subject: Re: linux-next: build warning after merge of the akpm-current tree
On Thu, 2019-08-01 at 08:15 +0200, Michal Hocko wrote:
> On Thu 01-08-19 15:51:30, Stephen Rothwell wrote:
> > Hi Miles,
> >
> > On Wed, 31 Jul 2019 14:28:04 +0800 Miles Chen <miles.chen@...iatek.com> wrote:
> > >
> > > On Wed, 2019-07-31 at 16:11 +1000, Stephen Rothwell wrote:
> > > >
> > > > After merging the akpm-current tree, today's linux-next build (powerpc
> > > > ppc64_defconfig) produced this warning:
> > > >
> > > > mm/memcontrol.c: In function 'invalidate_reclaim_iterators':
> > > > mm/memcontrol.c:1160:11: warning: suggest parentheses around assignment used as truth value [-Wparentheses]
> > > > } while (memcg = parent_mem_cgroup(memcg));
> > > > ^~~~~
> > > >
> > >
> > > Hi Stephen,
> > >
> > > Thanks for the telling me this. Sorry for the build warning.
> > > Should I send patch v5 to the mailing list to fix this?
> >
> > You might as well (cc'ing Andrew, of course).
> >
> > I would suggest finishing that loop like this:
> >
> > memcg = parent_mem_cgroup(memcg);
> > } while (memcg);
> >
> > rather than adding a set of parentheses.
thanks for the advise
>
> Qian has already posted a patch http://lkml.kernel.org/r/1564580753-17531-1-git-send-email-cai@lca.pw
Thanks Qian's quick fix.
It's the first time that I receive a build warning after the patch has
been merged to -mm tree. The build warning had been fixed by Qian,
should I send another change for this?
Powered by blists - more mailing lists