[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b2b86520904301504m2906e466ndd8b9e7851bcd59@mail.gmail.com>
Date: Thu, 30 Apr 2009 23:04:21 +0100
From: Alan Jenkins <sourcejedi.lkml@...glemail.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
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 7/7] kconfig: search for a config to base the
local(mod|yes)config on
On 4/30/09, Steven Rostedt <rostedt@...dmis.org> wrote:
> From: Steven Rostedt <srostedt@...hat.com>
>
> Instead of using the .config in the local directory. This patch
> changes streamline_config.pl to search various locations for a config.
>
> Here's the list and order of search:
>
> /proc/config.gz
> /boot/vmlinuz-`uname -r`
> vmlinux # local to the directory
> /lib/modules/`uname -r`/kernel/kernel/configs.ko
> kernel/configs.ko
> kernel/configs.o
> .config
>
> Once it finds a file that contains a config (it checks if the binary
> objects have configs first) it then uses it to create the .config
> with minimum modules needed.
Maybe this has already been discussed, but is there some reason for
omitting /boot/config-`uname -r`? My understanding as a user of a
specific distribution was that kernel packages provide these files,
and therefore do not feel the need to enable CONFIG_IKCONFIG.
Regards
Alan
--
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