From: Valdis.Kletnieks@vt.edu
To: david@lang.hm
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
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 11:26:38 -0500 [thread overview]
Message-ID: <14241.1230913598@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 02 Jan 2009 08:51:28 PST." <alpine.DEB.1.10.0901020849180.20509@asgard.lang.hm>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Fri, 02 Jan 2009 08:51:28 PST, david@lang.hm said:
> having things outside of the embedded menu depend on embedded makes it
> hard for people to figure out what they need to do to disable specific
> things.
Odd, I can do a 'make menuconfig', do a /EARLY_PRINTK, and see:
Symbol: EARLY_PRINTK [=y] x
x Prompt: Early printk x
x Defined at arch/x86/Kconfig.debug:33 x
x Depends on: EMBEDDED x
x Location: x
x -> Kernel hacking
> if you follow the logic you are providing to it's logical conclusion you
> may as well put all kernel config options under "I really know what I'm
> doing" top level lockout
Hey, I didn't make up that logic. ;)
A large percentage of the kernel config options are things that really *could*
be one way or the other for any given system. Maybe you want ext4, maybe you
don't. Maybe you need process accounting, maybe you don't. So they don't go
under EMBEDDED. But we can be 98% sure that they probably want PRINTK.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-01-02 16:27 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
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 [this message]
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=14241.1230913598@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bdonlan@gmail.com \
--cc=david@lang.hm \
--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®