[Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes?
Randy Dunlap
rdunlap at infradead.org
Thu Jul 6 17:11:26 UTC 2017
On 07/06/2017 09:41 AM, Linus Torvalds wrote:
> On Thu, Jul 6, 2017 at 7:40 AM, Dan Carpenter <dan.carpenter at oracle.com> wrote:
>> People have mentioned "make oldconfig" but I've never had a lot of luck
>> with that. It always just prints "* Restart config..." and deletes my
>> config.
>
> Really?
>
> For me, "make oldconfig" is pretty much the only thing I ever use
> (apart from build testing).
>
> It's very convenient once you have a baseline, and want to just get
> the new questions for when the Kconfig files change. It's also how I
> notice when somebody adds a new config entry that doesn't default to
> 'n'.
>
> It's also very convenient when you end up changing your config: just
> edit the damn .config file directly, and then re-run "make oldconfig"
> just to make sure everything gets updated (and then you'll notice that
> you tried to disable some config entry, but it got re-enabled again
> because there was something else that depended on it and selected it
> ;)
>
> So I wonder why it wouldn't work for you.
>
> Now, admittedly, I literally only ever use two source files: the
> previous ".config" file, and if that is missing (after a "git clean
> -dqfx" or similar), just /etc/kernel-config.
>
> The oldconfig logic has fallbacks to other cases, but they are all useless imho.
>
> Also, I build in the source tree. Maybe you use a separate object tree
> and it gets that case wrong.
Nah, I use O=objdir all the time and oldconfig works for me.
--
~Randy
More information about the Ksummit-discuss
mailing list