Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753926Ab0GUUel (ORCPT ); Wed, 21 Jul 2010 16:34:41 -0400 Received: from wolverine01.qualcomm.com ([199.106.114.254]:35943 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906Ab0GUUei (ORCPT ); Wed, 21 Jul 2010 16:34:38 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6050"; a="48203896" Subject: Re: [PATCH 2/4] mm: cma: Contiguous Memory Allocator added From: Daniel Walker To: =?UTF-8?Q?Micha=C5=82?= Nazarewicz Cc: linux-mm@kvack.org, Marek Szyprowski , Pawel Osciak , Xiaolin Zhang , Hiremath Vaibhav , Robert Fekete , Marcus Lorentzon , linux-kernel@vger.kernel.org, Kyungmin Park , linux-arm-msm@vger.kernel.org In-Reply-To: References: <1279649724.26765.23.camel@c-dwalke-linux.qualcomm.com> <1279654698.26765.31.camel@c-dwalke-linux.qualcomm.com> <1279733750.31376.14.camel@c-dwalke-linux.qualcomm.com> <1279736348.31376.20.camel@c-dwalke-linux.qualcomm.com> <1279738688.31376.24.camel@c-dwalke-linux.qualcomm.com> <1279741029.31376.33.camel@c-dwalke-linux.qualcomm.com> <1279742604.31376.40.camel@c-dwalke-linux.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 21 Jul 2010 13:34:32 -0700 Message-ID: <1279744472.31376.42.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1434 Lines: 35 On Wed, 2010-07-21 at 22:22 +0200, Michał Nazarewicz wrote: > On Wed, 21 Jul 2010 22:03:24 +0200, Daniel Walker wrote: > > > On Wed, 2010-07-21 at 21:53 +0200, Michał Nazarewicz wrote: > >> On Wed, 21 Jul 2010 21:37:09 +0200, Daniel Walker wrote: > >> > What makes you assume that the bootloader would have these strings? > >> > Do your devices have these strings? Maybe mine don't have them. > >> > >> I don't assume. I only state it as one of the possibilities. > >> > >> > Assume the strings are gone and you can't find them, or have no idea > >> > what they should be. What do you do then? > >> > >> Ask Google? > > > > Exactly, that's why they need to be in the kernel .. > > Right..... Please show me a place where I've written that it won't be in > the kernel? I keep repeating command line is only one of the possibilities. > I would imagine that in final product defaults from platform would be used > and bootloader would be left alone. It should never be anyplace else. Daniel -- Sent by an consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/