From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Arnd Bergmann To: Stephen Boyd Cc: James Liao , linux-arm-kernel@lists.infradead.org, kbuild test robot , srv_heupstream@mediatek.com, devicetree@vger.kernel.org, Mike Turquette , linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, kbuild-all@01.org, Sascha Hauer , Matthias Brugger , linux-clk@vger.kernel.org Subject: Re: [PATCH] clk: Move vendor's Kconfig into CCF menu section Date: Thu, 28 Jan 2016 12:31:59 +0100 Message-ID: <1505403.Puq3Qui8Zr@wuerfel> In-Reply-To: <20160128083656.GM12841@codeaurora.org> References: <201601271708.gQUxXACW%fengguang.wu@intel.com> <6167008.u8jfFpmfhy@wuerfel> <20160128083656.GM12841@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" List-ID: On Thursday 28 January 2016 00:36:56 Stephen Boyd wrote: > On 01/27, Arnd Bergmann wrote: > > On Wednesday 27 January 2016 17:56:18 James Liao wrote: > > > > > > > > I think you should include this change in your patch, or as a preparation. > > > > All other samsung platforms already select COMMON_CLK through ARCH_MULTIPLATFORM, > > > > and all SoCs that are part of ARCH_S3C24XX individually select a symbol that > > > > selects COMMON_CLK. > > > > > > Oops, I didn't notice there are warnings after moving these Kconfigs > > > into menu section. > > > > > > The original motivation of this patch is preventing new clk drivers > > > include their Kconfig in a wrong place, so it's not critical. Do you > > > think we should apply this patch (with your changes below) or drop this > > > patch directly? > > > > > > I think your patch is good, we just need to fix S3C24xx, which is doing > > things in a strange way for historic reasons. > > So far we've taken the approach of not caring if they include > their Kconfig outside the common clk menu when all the configs > inside the Kconfig file are hidden. Of course, when they aren't > hidden this becomes a problem, but that isn't the case unless > something changed recently. They are all hidden, but there is no real reason for that I think (other than the samsung glitch). Having them inside the menu makes it possible to add '|| COMPILE_TEST' as a follow-up, and makes it more consistent overall. Arnd