From: Matt Mackall <mpm@selenic.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Tim Bird <tim.bird@am.sony.com>, linux-kernel@vger.kernel.org
Subject: Re: FASTBOOT options in EMBEDDED menu?
Date: Tue, 2 Mar 2004 01:58:26 -0600 [thread overview]
Message-ID: <20040302075826.GX3883@waste.org> (raw)
In-Reply-To: <20040301112435.66be3bcc.rddunlap@osdl.org>
On Mon, Mar 01, 2004 at 11:24:35AM -0800, Randy.Dunlap wrote:
> On Mon, 01 Mar 2004 11:19:55 -0800 Tim Bird wrote:
>
> | I'm starting to adapt some patches for options which
> | allow Linux to boot faster (for embedded environments).
> |
> | It seems like these should go under the EMBEDDED
> | menu. However, this menu looks like it is specific
> | to size reductions:
> |
> | menuconfig EMBEDDED
> | bool "Remove kernel features (for embedded systems)"
> | help
> | This option allows certain base kernel features to be removed from
> | the build...
> |
> | Some of the options that CELF is working on for
> | fast booting do remove features, but some do not.
> |
> | Anyone have advice for whether I should:
> | 1) use the existing EMBEDDED option (my preference), or
> | 2) make a new FASTBOOT option?
>
> I agree with you, EMBEDDED should be able to handle it.
I've renamed the EMBEDDED menu in my tree to something on the order of
"modify standard feature set" as it's not really specific to EMBEDDED.
Tim, if you want to send me your fastboot patches, I'd be happy to put
them in -tiny.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
prev parent reply other threads:[~2004-03-02 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 19:19 FASTBOOT options in EMBEDDED menu? Tim Bird
2004-03-01 19:24 ` Randy.Dunlap
2004-03-02 7:58 ` Matt Mackall [this message]
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=20040302075826.GX3883@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=tim.bird@am.sony.com \
/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