From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH][RFC] x86: add non x86 build configuration
Date: Thu, 30 Oct 2008 21:55:26 +0100 [thread overview]
Message-ID: <20081030205526.GB24626@elte.hu> (raw)
In-Reply-To: <20081030202006.GA1255@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> > So please name it something like CONFIG_STANDARD_X86_FEATURES, and
> > also make it depend on CONFIG_EMBEDDED (only allow it to be turned
> > off when EMBEDDED is enabled).
>
> Any chance to introduce a CONFIG_EXPERT option?
>
> CONFIG_EMBEDDED is supposed to be those features that may decrease
> performance or functionality but lower the footprint. And not all
> the crap it covers today.
turning those features off will reduce the kernel's size as well - so
i think it's appropriate in this specific case.
but i agree with your general point that CONFIG_EMBEDDED is abused in
a few cases.
Ingo
prev parent reply other threads:[~2008-10-30 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810281802.m9SI2fYX030138@hera.kernel.org>
2008-10-29 9:18 ` ftrace: fix depends Heiko Carstens
2008-10-29 15:15 ` [PATCH] ftrace: fix trace_nop config select Steven Rostedt
2008-10-29 16:21 ` Ingo Molnar
2008-10-30 1:43 ` [PATCH][RFC] x86: add non x86 build configuration Steven Rostedt
2008-10-30 19:51 ` Ingo Molnar
2008-10-30 20:05 ` Steven Rostedt
2008-10-30 20:57 ` Ingo Molnar
2008-10-30 21:09 ` Steven Rostedt
2008-10-30 20:20 ` Sam Ravnborg
2008-10-30 20:55 ` Ingo Molnar [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=20081030205526.GB24626@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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