From: Valdis.Kletnieks@vt.edu
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, 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, 02 Jan 2009 10:39:12 -0500 [thread overview]
Message-ID: <11444.1230910752@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 02 Jan 2009 20:40:16 +0530." <3f9a31f40901020710h508bbfbch3d7ccd6f4898ea03@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Fri, 02 Jan 2009 20:40:16 +0530, Jaswinder Singh Rajput said:
> If I know what is my CPU there is no point for supporting all related
> CPUs in my kernel.
EMBEDDED is for a large assortment of things, all of which are of the form:
General users won't want to change Y, but if I know I don't need Y, there is
no point in supporting Y in the kernel.
Y might be "this kernel doesn't need sysctl"
Y might be "support for hot-plug"
Y might be "printk"
Y might be "support generic CPUs"
See the pattern?
Yes, we probably could have come up with a better name than EMBEDDED for
that list of optionals.
CONFIG_TRAINED_TECHNICIANS_ONLY_NO_USER_SERVICABLE_PARTS_INSIDE maybe?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-01-02 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 20:37 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 [this message]
2009-01-02 16:13 ` Jaswinder Singh Rajput
2009-01-02 16:20 ` Valdis.Kletnieks
2009-01-02 16:23 ` Ingo Molnar
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=11444.1230910752@turing-police.cc.vt.edu \
--to=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=mingo@elte.hu \
--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®