From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Create a top-level "Space-critical features" menu.
Date: Tue, 8 May 2007 04:27:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705080421540.13343@localhost.localdomain> (raw)
In-Reply-To: <1178612519.3042.294.camel@localhost.localdomain>
On Tue, 8 May 2007, Thomas Gleixner wrote:
> On Tue, 2007-05-08 at 04:06 -0400, Robert P. J. Day wrote:
> > i've always hated that lower-level menu under "General setup":
>
> Good reason to break everything which depends on CONFIG_EMBEDDED.
>
> tglx
>
> > -menuconfig EMBEDDED
> > - bool "Configure standard kernel features (for small systems)"
i don't know what you're getting at here. are you saying this is a
bad idea because it will make a mess of the current usage of
CONFIG_EMBEDDED in the source tree?
$ grep -rw CONFIG_EMBEDDED *
... lots of irrelevant defconfig output deleted ...
drivers/pci/setup-res.c:#ifdef CONFIG_EMBEDDED
include/linux/ide.h:#if !defined(MAX_HWIFS) || defined(CONFIG_EMBEDDED)
$
i don't see a whole lot of impact here. more to the point, though,
the word "EMBEDDED" in this context is just wrong. people might have
*other* reasons to de-activate some of those features rather than just
for an embedded system.
granted, that's probably where it will *mostly* happen, but i prefer
the idea of labelling those selections for what they really are -- for
*saving* *space*, because that's exactly what they represent.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-08 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:06 Robert P. J. Day
2007-05-08 8:21 ` Thomas Gleixner
2007-05-08 8:27 ` Robert P. J. Day [this message]
2007-05-08 8:37 ` Thomas Gleixner
2007-05-08 8:41 ` Robert P. J. Day
2007-05-08 9:21 ` Jan Engelhardt
2007-05-08 13:03 ` Stefan Richter
2007-05-08 16:19 ` Robert P. J. Day
2007-05-08 20:22 ` Matt Mackall
2007-05-08 8:56 ` Adrian Bunk
2007-05-08 16:14 ` Robert P. J. Day
2007-05-08 20:10 ` Matt Mackall
2007-05-08 20:34 ` Robert P. J. Day
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=Pine.LNX.4.64.0705080421540.13343@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®