[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANMq1KDT1WpPksLw5M0OyujF2XnSM0F7gkhWLi4VAa6je48qsw@mail.gmail.com>
Date: Tue, 21 May 2019 16:06:26 +0800
From: Nicolas Boichat <drinkcat@...omium.org>
To: kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...org, Andrew Morton <akpm@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Michal Hocko <mhocko@...e.com>, Joe Perches <joe@...ches.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-mm@...ck.org, Akinobu Mita <akinobu.mita@...il.com>,
Pekka Enberg <penberg@...nel.org>,
Mel Gorman <mgorman@...hsingularity.net>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/failslab: By default, do not fail allocations with
direct reclaim only
On Tue, May 21, 2019 at 4:01 PM kbuild test robot <lkp@...el.com> wrote:
> sparse warnings: (new ones prefixed by >>)
>
> >> mm/failslab.c:27:26: sparse: sparse: restricted gfp_t degrades to integer
> 26 if (failslab.ignore_gfp_reclaim &&
> > 27 (gfpflags & ___GFP_DIRECT_RECLAIM))
That was for v1, fixed in v2 already.
Powered by blists - more mailing lists