From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932265Ab1GEMH1 (ORCPT ); Tue, 5 Jul 2011 08:07:27 -0400 Received: from moutng.kundenserver.de ([212.227.17.8]:56347 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756109Ab1GEMH0 (ORCPT ); Tue, 5 Jul 2011 08:07:26 -0400 From: Arnd Bergmann To: Marek Szyprowski Subject: Re: [PATCHv11 0/8] Contiguous Memory Allocator Date: Tue, 5 Jul 2011 14:07:17 +0200 User-Agent: KMail/1.12.2 (Linux/2.6.37; KDE/4.3.2; x86_64; ; ) Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org, linux-mm@kvack.org, linaro-mm-sig@lists.linaro.org, Michal Nazarewicz , Kyungmin Park , Andrew Morton , KAMEZAWA Hiroyuki , Ankita Garg , Daniel Walker , Mel Gorman , Jesse Barker , Jonathan Corbet , Chunsang Jeong References: <1309851710-3828-1-git-send-email-m.szyprowski@samsung.com> In-Reply-To: <1309851710-3828-1-git-send-email-m.szyprowski@samsung.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201107051407.17249.arnd@arndb.de> X-Provags-ID: V02:K0:aKisnNNFP5Z9qA9Q+4Vs6DW+TVhtOqI31UOIKfinkN+ VZoGwro3rHCSSIZsuiX8pyQb1j7CoU0HgMs9gy2WHTq7+a5ggP a5Yryh2O7W1m038w2XBu4nc/W+VMOFFtjxR4BM4MbZWpSTHest VafrE8gptM7aA67fAPW3M1FfAOgX5WJdwXPwGYMrFrsB6MmVAJ mi4VWBh1QdsIRlx00rEDg== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 05 July 2011, Marek Szyprowski wrote: > This is yet another round of Contiguous Memory Allocator patches. I hope > that I've managed to resolve all the items discussed during the Memory > Management summit at Linaro Meeting in Budapest and pointed later on > mailing lists. The goal is to integrate it as tight as possible with > other kernel subsystems (like memory management and dma-mapping) and > finally merge to mainline. You have certainly addressed all of my concerns, this looks really good now! Andrew, can you add this to your -mm tree? What's your opinion on the current state, do you think this is ready for merging in 3.1 or would you want to have more reviews from core memory management people? My reviews were mostly on the driver and platform API side, and I think we're fine there now, but I don't really understand the impacts this has in mm. Arnd