From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753300AbbCXHjX (ORCPT ); Tue, 24 Mar 2015 03:39:23 -0400 Received: from mail.emea.novell.com ([130.57.118.101]:39779 "EHLO mail.emea.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751665AbbCXHjT convert rfc822-to-8bit (ORCPT ); Tue, 24 Mar 2015 03:39:19 -0400 Message-Id: <551122B4020000780006CD28@mail.emea.novell.com> X-Mailer: Novell GroupWise Internet Agent 14.0.1 Date: Tue, 24 Mar 2015 07:39:16 +0000 From: "Jan Beulich" To: "Paul Bolle" , "Martin Walch" Cc: , "Sam Ravnborg" , "Michal Marek" , , Subject: Re: [PATCH] Kconfig: drop bogus default values References: <5500584D02000078000688F5@mail.emea.novell.com> <178407860.0zoJnDfCo1@tacticalops> <1427145868.10958.5.camel@x220> <1565998.uAQ7oZ5VxV@tacticalops> In-Reply-To: <1565998.uAQ7oZ5VxV@tacticalops> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>> On 23.03.15 at 23:58, wrote: > 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. If the "n" default was really needed, it could be config PCI_QUIRKS default !S390 Jan