From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id F0CED901 for ; Thu, 6 Jul 2017 17:49:10 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6EAB08D for ; Thu, 6 Jul 2017 17:49:10 +0000 (UTC) To: Linus Torvalds , Dan Carpenter References: <20170627135839.GB1886@jagdpanzerIV.localdomain> <20170706144028.46a2mt2mdzpt6ip7@mwanda> From: Randy Dunlap Message-ID: <966c1fce-6f2f-d158-d086-cf8e2eac97a9@infradead.org> Date: Thu, 6 Jul 2017 10:11:26 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Cc: ksummit , Michal Hocko Subject: Re: [Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 07/06/2017 09:41 AM, Linus Torvalds wrote: > On Thu, Jul 6, 2017 at 7:40 AM, Dan Carpenter 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