From: Tim Bird <tim.bird@am.sony.com>
To: Paul Mundt <lethal@linux-sh.org>, Tim Bird <tim.bird@am.sony.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] init: support preset lpj value as config option
Date: Thu, 25 Jan 2007 10:24:59 -0800 [thread overview]
Message-ID: <45B8F5FB.6090704@am.sony.com> (raw)
In-Reply-To: <20070125021847.GA7609@linux-sh.org>
Paul Mundt wrote:
> On Wed, Jan 24, 2007 at 04:12:18PM -0800, Tim Bird wrote:
>> This patch provides a config option for preset lpj, which means
>> the value can be easily preserved, and conveyed between developers
>> in a config file.
>>
> This seems excessive, it's already possible to set the preset lpj on the
> kernel command line, and virtually every one of the embedded
> architectures supports setting the kernel command line as a config
> option. Is there any reason why you can't simply set it there as a
> default instead? It's all going to be .config resident in the end
> anyways.
i386 is missing CONFIG_CMDLINE support, and this architecture
is used in embedded. I think many other x86 derivatives are
also missing .config-based command line support. CELF has
worked to get patches submitted to fix this, but so far these
haven't been accepted.
For this reason (and IMHO from the standpoint of orthogonality)
I think it's awkward to have options which ONLY have a command-line
representation, and not a way to compile them in separately.
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
next prev parent reply other threads:[~2007-01-25 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 0:12 [PATCH] init: support preset lpj value as config option Tim Bird
2007-01-25 2:18 ` Paul Mundt
2007-01-25 18:24 ` Tim Bird [this message]
2007-01-26 10:44 ` Andrew Morton
2007-01-26 18:29 ` Tim Bird
2007-01-26 18:46 ` Matt Mackall
2007-01-26 19:02 ` H. Peter Anvin
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=45B8F5FB.6090704@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
/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