From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758301Ab3GZDIW (ORCPT ); Thu, 25 Jul 2013 23:08:22 -0400 Received: from mail-ve0-f173.google.com ([209.85.128.173]:54186 "EHLO mail-ve0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755919Ab3GZDIR (ORCPT ); Thu, 25 Jul 2013 23:08:17 -0400 Date: Thu, 25 Jul 2013 23:08:12 -0400 From: Tejun Heo To: Santosh Shilimkar Cc: Yinghai Lu , Russell King - ARM Linux , linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List , Catalin Marinas , Will Deacon , Nicolas Pitre , Ingo Molnar , Andrew Morton , "H. Peter Anvin" , Benjamin Herrenschmidt , Paul Mackerras , "David S. Miller" , "sparclinux@vger.kernel.org" , Sam Ravnborg , linux-arch@vger.kernel.org Subject: Re: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM Message-ID: <20130726030812.GB30195@mtj.dyndns.org> References: <20130629152959.GB31339@mtj.dyndns.org> <20130629172123.GA3353@n2100.arm.linux.org.uk> <20130629175743.GA382@mtj.dyndns.org> <20130629195549.GE3353@n2100.arm.linux.org.uk> <51D18DBA.6090608@ti.com> <51F1A7AA.8080700@ti.com> <20130725223658.GJ26107@mtj.dyndns.org> <51F1B17F.30902@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51F1B17F.30902@ti.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Thu, Jul 25, 2013 at 07:15:11PM -0400, Santosh Shilimkar wrote: > Sorry if I wasn't clear before, but I need help to at least have new > memblock API support since I am not familiar with memblock code. > I could help in adaptation to the new API for ARM arch and > core kernel code. > > Let me know your thoughts. Unfortunately, I'm currently a bit too occupied to work on it myself. Any volunteers? Thanks. -- tejun From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Date: Fri, 26 Jul 2013 03:08:12 +0000 Subject: Re: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM Message-Id: <20130726030812.GB30195@mtj.dyndns.org> List-Id: References: <20130629152959.GB31339@mtj.dyndns.org> <20130629172123.GA3353@n2100.arm.linux.org.uk> <20130629175743.GA382@mtj.dyndns.org> <20130629195549.GE3353@n2100.arm.linux.org.uk> <51D18DBA.6090608@ti.com> <51F1A7AA.8080700@ti.com> <20130725223658.GJ26107@mtj.dyndns.org> <51F1B17F.30902@ti.com> In-Reply-To: <51F1B17F.30902@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Santosh Shilimkar Cc: Yinghai Lu , Russell King - ARM Linux , linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List , Catalin Marinas , Will Deacon , Nicolas Pitre , Ingo Molnar , Andrew Morton , "H. Peter Anvin" , Benjamin Herrenschmidt , Paul Mackerras , "David S. Miller" , "sparclinux@vger.kernel.org" , Sam Ravnborg , linux-arch@vger.kernel.org Hello, On Thu, Jul 25, 2013 at 07:15:11PM -0400, Santosh Shilimkar wrote: > Sorry if I wasn't clear before, but I need help to at least have new > memblock API support since I am not familiar with memblock code. > I could help in adaptation to the new API for ARM arch and > core kernel code. > > Let me know your thoughts. Unfortunately, I'm currently a bit too occupied to work on it myself. Any volunteers? Thanks. -- tejun From mboxrd@z Thu Jan 1 00:00:00 1970 From: tj@kernel.org (Tejun Heo) Date: Thu, 25 Jul 2013 23:08:12 -0400 Subject: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM In-Reply-To: <51F1B17F.30902@ti.com> References: <20130629152959.GB31339@mtj.dyndns.org> <20130629172123.GA3353@n2100.arm.linux.org.uk> <20130629175743.GA382@mtj.dyndns.org> <20130629195549.GE3353@n2100.arm.linux.org.uk> <51D18DBA.6090608@ti.com> <51F1A7AA.8080700@ti.com> <20130725223658.GJ26107@mtj.dyndns.org> <51F1B17F.30902@ti.com> Message-ID: <20130726030812.GB30195@mtj.dyndns.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello, On Thu, Jul 25, 2013 at 07:15:11PM -0400, Santosh Shilimkar wrote: > Sorry if I wasn't clear before, but I need help to at least have new > memblock API support since I am not familiar with memblock code. > I could help in adaptation to the new API for ARM arch and > core kernel code. > > Let me know your thoughts. Unfortunately, I'm currently a bit too occupied to work on it myself. Any volunteers? Thanks. -- tejun