[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090501120100.GC24706@elte.hu>
Date: Fri, 1 May 2009 14:01:00 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Theodore Tso <tytso@....edu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
zippel@...ux-m68k.org, linux-kbuild@...r.kernel.org,
Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH 0/7] kconfig: more featured minimum module configs
* Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 30 Apr 2009, Ingo Molnar wrote:
>
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > > This set of patches adds on top of my previous post.
> > >
> > > It fixes CONFIG_IKCONFIG when CONFIG_IKCONFIG_PROC is not set.
> > > (gcc optimizes the config out!)
> > >
> > > As a request from Ingo, it now enables IKCONFIG and will also use
> > > various locations to find a config to base against.
> >
> > hm, now 'make localyesconfig' done on a Fedora distro kernel
> > produces something very close to an allyesconfig:
> >
> > -rw-rw-r-- 1 mingo mingo 91930 2009-04-30 20:03 .config
> > aldebaran:~/linux/linux> grep =y .config | wc -l
> > 3398
> >
> > is that expected?
>
> What config did it use? If it uses an allyesconfig that was
> already made then it will not disable anything.
i used a regular config - then i also tried an allnoconfig - but no
change in the result, bloated .config.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists