Messages in this thread | | | Date | Thu, 12 Mar 2015 12:36:45 +0000 | From | "Jan Beulich" <> | Subject | Re: [PATCH] Kconfig: drop bogus default values |
| |
>>> On 12.03.15 at 13:11, <pebolle@tiscali.nl> wrote: > On Wed, 2015-03-11 at 13:59 +0000, Jan Beulich wrote: >> Default "no" is pretty pointless for options without (visible) prompts: > > Related: is there ever a situation where using "default n" or "def_bool > n" makes sense (whether or not the entry has a prompt)? I think I once > thought of one but I can't remember it at all, so I guess my memory is > fooling me.
I can't see any, but since as long as there is a visible prompt this doesn't have any other bad effect than bloating the Kconfig file and making its parsing a tiny bit slower, I don't care that much about those (originally I had started a patch removing those too, but gave up after a while).
Jan
| |