Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-21 Thread Joonsoo Kim
On Fri, Dec 08, 2017 at 02:37:19PM -0800, Andrew Morton wrote: > On Fri, 1 Dec 2017 16:53:03 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > v2 > > o previous failure in linux-next turned out that it's not the problem of > > this patchset. It was caused by

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-21 Thread Joonsoo Kim
On Fri, Dec 08, 2017 at 02:37:19PM -0800, Andrew Morton wrote: > On Fri, 1 Dec 2017 16:53:03 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > 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

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-08 Thread Andrew Morton
On Fri, 1 Dec 2017 16:53:03 +0900 js1...@gmail.com wrote: > From: Joonsoo Kim > > 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. > >

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-08 Thread Andrew Morton
On Fri, 1 Dec 2017 16:53:03 +0900 js1...@gmail.com wrote: > From: Joonsoo Kim > > 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. > >

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-05 Thread Tony Lindgren
* js1...@gmail.com [171201 07:55]: > From: Joonsoo Kim > > 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. > >

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-05 Thread Tony Lindgren
* js1...@gmail.com [171201 07:55]: > From: Joonsoo Kim > > 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.ga28...@atomide.com Thanks works me,

[PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-11-30 Thread js1304
From: Joonsoo Kim 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.ga28...@atomide.com o add missing cache flush to the patch "ARM:

[PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-11-30 Thread js1304
From: Joonsoo Kim 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.ga28...@atomide.com o add missing cache flush to the patch "ARM: CMA: avoid double