[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171205164800.GV28152@atomide.com>
Date: Tue, 5 Dec 2017 08:48:00 -0800
From: Tony Lindgren <tony@...mide.com>
To: js1304@...il.com
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Johannes Weiner <hannes@...xchg.org>,
Laura Abbott <lauraa@...eaurora.org>,
Minchan Kim <minchan@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Michal Nazarewicz <mina86@...a86.com>,
"Aneesh Kumar K . V" <aneesh.kumar@...ux.vnet.ibm.com>,
Vlastimil Babka <vbabka@...e.cz>,
Russell King <linux@...linux.org.uk>,
Will Deacon <will.deacon@....com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, kernel-team@....com,
Joonsoo Kim <iamjoonsoo.kim@....com>
Subject: Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by
using the ZONE_MOVABLE
* js1304@...il.com <js1304@...il.com> [171201 07:55]:
> From: Joonsoo Kim <iamjoonsoo.kim@....com>
>
> v2
> o previous failure in linux-next turned out that it's not the problem of
> this patchset. It was caused by the wrong assumption by specific
> architecture.
>
> lkml.kernel.org/r/20171114173719.GA28152@...mide.com
Thanks works me, I've sent a pull request for the related fix for
v4.15-rc cycle. So feel free to add for the whole series:
Tested-by: Tony Lindgren <tony@...mide.com>
Powered by blists - more mailing lists