From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Theodore Tso <tytso@mit.edu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
zippel@linux-m68k.org, linux-kbuild@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 0/3] removing unwanted module configs
Date: Thu, 30 Apr 2009 09:47:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0904300945440.20374@gandalf.stny.rr.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0904300932380.20374@gandalf.stny.rr.com>
On Thu, 30 Apr 2009, Steven Rostedt wrote:
>
> Since this option can also be used for helping embedded developers (I used
> it for that) I would not want to bloat the kernel with running a script
> that is suppose to minimize it. But if IKCONFIG && !IKCONFIG_PROC does not
> add more data to the kernel, then I would be happy to turn it on by
> default.
Actually, I can let the user decide. If it sees that IKCONFIG is not set,
it can remove it from the .config output. When the silentoldconfig runs
afterwards, it will ask the user if they want to enable it.
-- Steve
next prev parent reply other threads:[~2009-04-30 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 3:08 [PATCH 0/3] removing unwanted module configs Steven Rostedt
2009-04-30 3:08 ` [PATCH 1/3] kconfig: add streamline_config.pl to scripts Steven Rostedt
2009-04-30 3:08 ` [PATCH 2/3] kconfig: make localmodconfig to run streamline_config.pl Steven Rostedt
2009-04-30 3:08 ` [PATCH 3/3] kconfig: add make localyesconfig option Steven Rostedt
2009-04-30 7:18 ` [PATCH 0/3] removing unwanted module configs Ingo Molnar
2009-04-30 13:17 ` Steven Rostedt
2009-04-30 13:26 ` Ingo Molnar
2009-04-30 13:42 ` Steven Rostedt
2009-04-30 13:47 ` Steven Rostedt [this message]
2009-04-30 14:43 ` Ingo Molnar
2009-04-30 14:42 ` Ingo Molnar
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=alpine.DEB.2.00.0904300945440.20374@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).