linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rik van Riel <riel@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	mgorman@techsingularity.net, Laura Abbott <lauraa@codeaurora.org>,
	Minchan Kim <minchan@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Michal Nazarewicz <mina86@mina86.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/6] Introduce ZONE_CMA
Date: Mon, 28 Nov 2016 16:41:41 +0900	[thread overview]
Message-ID: <20161128074141.GB32105@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20161107062501.GB21159@js1304-P5Q-DELUXE>

On Mon, Nov 07, 2016 at 03:25:01PM +0900, Joonsoo Kim wrote:
> On Fri, Oct 14, 2016 at 12:03:10PM +0900, js1304@gmail.com wrote:
> > From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> > 
> > Hello,
> > 
> > Changes from v5
> > o Add acked/reviewed-by tag from Vlastimil and Aneesh
> > o Rebase on next-20161013
> > o Cosmetic change on patch 1
> > o Optimize span of ZONE_CMA on multiple node system
> 
> Hello, Andrew.
> 
> I got some acked/reviewed-by tags from some of main MM developers who
> are actually familiar/associated with this change. Could you merge
> this patchset to your tree to get more test coverage?
> 
> If I need to do more things to merge this patchset, please let me know
> about it.

Hello, Andrew.

Could I get your answer about this patchset?

Thanks.

      reply	other threads:[~2016-11-28  7:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  3:03 [PATCH v6 0/6] Introduce ZONE_CMA js1304
2016-10-14  3:03 ` [PATCH v6 1/6] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request js1304
2016-10-14  3:03 ` [PATCH v6 2/6] mm/cma: introduce new zone, ZONE_CMA js1304
2016-11-01  7:58   ` Chen Feng
2016-11-07  6:15     ` Joonsoo Kim
2016-11-07  7:08       ` Chen Feng
2016-11-07  7:27         ` Joonsoo Kim
2016-11-07  7:44           ` Chen Feng
2016-11-07  7:46             ` Chen Feng
2016-11-08  3:59               ` Joonsoo Kim
2016-11-08  6:59                 ` Chen Feng
2016-11-11  6:38                   ` Joonsoo Kim
2016-10-14  3:03 ` [PATCH v6 3/6] mm/cma: populate ZONE_CMA js1304
2016-10-18  7:42   ` Vlastimil Babka
2016-10-18  8:27     ` Joonsoo Kim
2016-10-26  4:31       ` Joonsoo Kim
2016-10-26  7:27         ` Vlastimil Babka
2016-10-14  3:03 ` [PATCH v6 4/6] mm/cma: remove ALLOC_CMA js1304
2016-10-14  3:03 ` [PATCH v6 5/6] mm/cma: remove MIGRATE_CMA js1304
2016-10-14  3:03 ` [PATCH v6 6/6] mm/cma: remove per zone CMA stat js1304
2016-11-07  6:25 ` [PATCH v6 0/6] Introduce ZONE_CMA Joonsoo Kim
2016-11-28  7:41   ` Joonsoo Kim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161128074141.GB32105@js1304-P5Q-DELUXE \
    --to=iamjoonsoo.kim@lge.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hannes@cmpxchg.org \
    --cc=lauraa@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mgorman@techsingularity.net \
    --cc=mina86@mina86.com \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.com \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).