public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Valdis.Kletnieks@vt.edu
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
	Bryan Donlan <bdonlan@gmail.com>,
	Ingo Brueckl <ib@wupperonline.de>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: x86 (Linux Tiny): configure out support for some processors
Date: Fri, 2 Jan 2009 17:23:57 +0100	[thread overview]
Message-ID: <20090102162357.GH1180@elte.hu> (raw)
In-Reply-To: <13903.1230913212@turing-police.cc.vt.edu>


* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:

> On Fri, 02 Jan 2009 21:43:03 +0530, Jaswinder Singh Rajput said:
> 
> > Let me know why should I choose EMBEDDED option ? I know I am not 
> > using Embbeded machine and I do not need embbeded features on my 
> > machine. If I am willing to go North why should I go South first ?
> 
> EMBEDDED is a bad name for the option.  It *started* as "only those 
> maniac who need to trim their kernel WAY down should select this", and 
> ended up as "stuff that 95% of users shouldn't change, but you can if 
> you know what you're doing".

i think both activities fit the generic 'embedded/specialized kernel' term 
quite well, so i dont think there's a big naming problem. There's maybe a 
documentation problem - the help text could be improved some more to 
signal that certain specialized config options are only available under 
CONFIG_EMBEDDED.

	Ingo

  reply	other threads:[~2009-01-02 16:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 20:37 x86 (Linux Tiny): configure out support for some processors Ingo Brueckl
2009-01-02  5:19 ` Bryan Donlan
2009-01-02  5:59   ` Jaswinder Singh Rajput
2009-01-02  9:38     ` Ingo Molnar
2009-01-02 15:10       ` Jaswinder Singh Rajput
2009-01-02 15:39         ` Valdis.Kletnieks
2009-01-02 16:13           ` Jaswinder Singh Rajput
2009-01-02 16:20             ` Valdis.Kletnieks
2009-01-02 16:23               ` Ingo Molnar [this message]
2009-01-02 16:21             ` Ingo Molnar
2009-01-02 16:38               ` Jaswinder Singh Rajput
2009-01-02 17:34                 ` Ingo Molnar
2009-01-02 18:13                   ` Replace CONFIG_EMBEDDED [Was: x86 (Linux Tiny): configure out support for some processor] Sam Ravnborg
2009-01-02 19:02                     ` Bill Davidsen
2009-01-02 19:31                       ` Sam Ravnborg
2009-01-02 16:51           ` x86 (Linux Tiny): configure out support for some processors david
2009-01-02 16:26             ` Valdis.Kletnieks
2009-01-02 18:54               ` david

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=20090102162357.GH1180@elte.hu \
    --to=mingo@elte.hu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=bdonlan@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ib@wupperonline.de \
    --cc=jaswinderlinux@gmail.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