From: Michal Marek <mmarek@suse.com>
To: Joe Perches <joe@perches.com>
Cc: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@iguana.be>,
Wolfram Sang <wsa@the-dreams.de>,
Robin Gong <b38343@freescale.com>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: kbuild: default n removals?
Date: Wed, 15 Jun 2016 12:02:36 +0200 [thread overview]
Message-ID: <576127BC.6050905@suse.com> (raw)
In-Reply-To: <1465400332.25087.56.camel@perches.com>
On 2016-06-08 17:38, Joe Perches wrote:
> (Adding Michal Marek and linux-kbuild)
>
> On Wed, 2016-06-08 at 18:11 +0300, Vladimir Zapolskiy wrote:
>> On 08.06.2016 16:53, Guenter Roeck wrote:
>>> On 06/08/2016 06:37 AM, Vladimir Zapolskiy wrote:
>>>>>> +comment "Watchdog Pretimeout Governors"
>>>>>> +
>>>>>> +config WATCHDOG_PRETIMEOUT_GOV
>>>>>> + bool "Enable watchdog pretimeout governors"
>>>>>> + default n
>>>>> I don't think 'default n" is needed.
>>>>>
>>>> No strict objections, but probably 'default n' may save quite many
>>>> lines in defconfigs.
>>>>
>>> I always wondered why it would be necessary to say "default n".
>>> What is the difference between "default n" and no explicit default ?
>>>
>> I pointed out that it may have impact on defconfig, but experimentally
>> it has no effect.
>>
>> Users of "make oldconfig" get a prompt in both cases as well.
>>
>> Also I haven't found any difference for silentoldconfig, olddefconfig
>> and alldefconfig, I assume explicit "default n" and "def_bool n"
>> can be safely dropped.
Yes, 'default n' is a noop.
> It's not completely clear removals are always appropriate.
>
> from: Documentation/kbuild/kconfig-language.txt:
> ------------------------------------------------------------------
> - default value: "default" <expr> ["if" <expr>]
> A config option can have any number of default values. If multiple
> default values are visible, only the first defined one is active.
> Default values are not limited to the menu entry where they are
> defined. This means the default can be defined somewhere else or be
> overridden by an earlier definition.
> The default value is only assigned to the config symbol if no other
> value was set by the user (via the input prompt above). If an input
> prompt is visible the default value is presented to the user and can
> be overridden by him.
> Optionally, dependencies only for this default value can be added with
> "if".
> ------------------------------------------------------------------
>
> Michal? Do you have an opinion or clarification?
As Guenter explained, there can be multiple default statements with
different if conditions. The first statement to match applies.
Michal
prev parent reply other threads:[~2016-06-15 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465321127-19522-1-git-send-email-vladimir_zapolskiy@mentor.com>
[not found] ` <1465321127-19522-5-git-send-email-vladimir_zapolskiy@mentor.com>
[not found] ` <20160607214309.GA17129@roeck-us.net>
[not found] ` <57581FB2.10806@mentor.com>
[not found] ` <57582363.8050406@roeck-us.net>
[not found] ` <5758358A.602@mentor.com>
2016-06-08 15:38 ` kbuild: default n removals? (was: Re: [PATCH v3 4/6] watchdog: add watchdog pretimeout framework) Joe Perches
2016-06-08 18:05 ` Guenter Roeck
2016-06-15 10:02 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=576127BC.6050905@suse.com \
--to=mmarek@suse.com \
--cc=b38343@freescale.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vladimir_zapolskiy@mentor.com \
--cc=wim@iguana.be \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox