From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) by lists.ozlabs.org (Postfix) with ESMTP id B82FE1A05AB for ; Thu, 19 Jun 2014 06:51:46 +1000 (EST) Date: Wed, 18 Jun 2014 13:51:44 -0700 From: Andrew Morton To: Joonsoo Kim Subject: Re: [PATCH v3 -next 0/9] CMA: generalize CMA reserved area management code Message-Id: <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> In-Reply-To: <20140617012507.GA6825@js1304-P5Q-DELUXE> References: <1402897251-23639-1-git-send-email-iamjoonsoo.kim@lge.com> <539EB4C7.3080106@samsung.com> <20140617012507.GA6825@js1304-P5Q-DELUXE> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: kvm-ppc@vger.kernel.org, Russell King - ARM Linux , kvm@vger.kernel.org, linux-mm@kvack.org, Gleb Natapov , Greg Kroah-Hartman , Alexander Graf , Michal Nazarewicz , linux-kernel@vger.kernel.org, Minchan Kim , Paul Mackerras , "Aneesh Kumar K.V" , Paolo Bonzini , Zhang Yanfei , linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, Marek Szyprowski List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote: > > >v2: > > > - Although this patchset looks very different with v1, the end result, > > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7. > > > > > >This patchset is based on linux-next 20140610. > > > > Thanks for taking care of this. I will test it with my setup and if > > everything goes well, I will take it to my -next tree. If any branch > > is required for anyone to continue his works on top of those patches, > > let me know, I will also prepare it. > > Hello, > > I'm glad to hear that. :) > But, there is one concern. As you already know, I am preparing further > patches (Aggressively allocate the pages on CMA reserved memory). It > may be highly related to MM branch and also slightly depends on this CMA > changes. In this case, what is the best strategy to merge this > patchset? IMHO, Anrew's tree is more appropriate branch. If there is > no issue in this case, I am willing to develope further patches based > on your tree. That's probably easier. Marek, I'll merge these into -mm (and hence -next and git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git) and shall hold them pending you review/ack/test/etc, OK?