From: Martin Walch <walch.martin@web.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Martin Walch <walch.martin@web.de>,
Jan Beulich <JBeulich@suse.com>,
akpm@linux-foundation.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] Kconfig: drop bogus default values
Date: Mon, 23 Mar 2015 23:58:52 +0100 [thread overview]
Message-ID: <1565998.uAQ7oZ5VxV@tacticalops> (raw)
In-Reply-To: <1427145868.10958.5.camel@x220>
On Monday 23 March 2015 22:24:28 Paul Bolle wrote:
> > A real world case is PCI_QUIRKS in the mainline kernel:
> >
> > init/Kconfig:1554: default y
> > arch/s390/Kconfig:59: def_bool n
> >
> > When setting PCI!=n && EXPERT=n then on each architecture PCI_QUIRKS=y
> > except on s390 where PCI_QUIRKS=n.
>
> Good catch!
>
> For the same effect, would it do to have
> config PCI_QUIRKS
> default y if !S390
> [...]
>
> in init/Kconfig?
Basically yes (although I suppose the maintainer had a good reason for
writing it the way it is now). But in the case with "def_bool n" in
arch/s390/Kconfig, the default value is explicitly set to n, while
"default y if !S390" does not set the value at all. As long as there are no
further default lines for PCI_QUIRKS below, this leads to the same
configuration. However if there was a third default line, then in the former
case that third default value would be always ignored while in the latter
case it would determine the default value on s390.
Regards,
Martin Walch
--
next prev parent reply other threads:[~2015-03-23 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 13:59 [PATCH] Kconfig: drop bogus default values Jan Beulich
2015-03-12 12:11 ` Paul Bolle
2015-03-12 12:36 ` Jan Beulich
2015-03-12 12:41 ` Paul Bolle
2015-03-12 18:51 ` Sam Ravnborg
2015-03-23 21:08 ` Martin Walch
2015-03-23 21:24 ` Paul Bolle
2015-03-23 22:58 ` Martin Walch [this message]
2015-03-24 7:39 ` Jan Beulich
2015-03-24 7:38 ` Jan Beulich
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=1565998.uAQ7oZ5VxV@tacticalops \
--to=walch.martin@web.de \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
--cc=sam@ravnborg.org \
/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