Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754450Ab0GUUpz (ORCPT ); Wed, 21 Jul 2010 16:45:55 -0400 Received: from wolverine01.qualcomm.com ([199.106.114.254]:41503 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753124Ab0GUUpw (ORCPT ); Wed, 21 Jul 2010 16:45:52 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6050"; a="48204962" 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> <1279744472.31376.42.camel@c-dwalke-linux.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 21 Jul 2010 13:45:43 -0700 Message-ID: <1279745143.31376.46.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: 1366 Lines: 29 On Wed, 2010-07-21 at 22:43 +0200, Michał Nazarewicz wrote: > > On Wed, 2010-07-21 at 22:22 +0200, Michał Nazarewicz wrote: > >> 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. > > On Wed, 21 Jul 2010 22:34:32 +0200, Daniel Walker wrote: > > It should never be anyplace else. > > I disagree. There are countless “dubug_level” kernel parameters or even > some “printk” related parameters. Those are completely hardware-independent. > There are also parameters that are hardware dependent but most users won't > care to set them. That's how the things are: there are some defaults but > you can override them by command line parameters. Your not hearing the issues.. IT'S TOO COMPLEX! Please remove it. 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/