[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1320987054.21206.55.camel@pasglop>
Date: Fri, 11 Nov 2011 15:50:54 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Timur Tabi <timur@...escale.com>
Cc: "Moffett, Kyle D" <Kyle.D.Moffett@...ing.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Baruch Siach <baruch@...s.co.il>,
Kumar Gala <galak@...nel.crashing.org>,
Scott Wood <scottwood@...escale.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Paul Mackerras <paulus@...ba.org>,
Wolfram Sang <w.sang@...gutronix.de>,
Grant Likely <grant.likely@...retlab.ca>,
Anatolij Gustschin <agust@...x.de>,
Paul Bolle <pebolle@...cali.nl>,
Sonny Rao <sonnyrao@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH 02/17] powerpc: Split up PHYS_64BIT config option to
fix "select" issues
On Thu, 2011-11-10 at 10:50 -0600, Timur Tabi wrote:
> I'm not sure that Kconfig rule is enforceable. We use 'select' all the time to make sure that our boards enable the options that need to be enabled. I'd rather see this:
>
> config X
> select A
>
> config Y
> select A
>
> config Z
> select A
>
> than this:
>
> config A
> default y if X | Y | Z
>
> The former is more maintainable and does not allow the option of disabling "A" if someone wants "X".
This is fine as long as config A is not a user selectable option.
We do the wrong thing in a few places (i2c comes to mind) and we should
most certainly consider fixing it. Some of the solution is to move some
select's to defconfigs, some is to do things the way Kyle proposed.
For PHYS_64BIT, I'm not 100% certain at this point what the best
approach it. It should clearly be fixed and hidden for real 64-bit. As
for the rest, should it be user selectable ? I tend to think it should
be fixed & selected by the board config and keep it that way, avoiding
the user question entirely... but you may have good reasons to want to
keep it around.
Cheers,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists