[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6167008.u8jfFpmfhy@wuerfel>
Date: Wed, 27 Jan 2016 11:32:29 +0100
From: Arnd Bergmann <arnd@...db.de>
To: James Liao <jamesjj.liao@...iatek.com>
Cc: linux-arm-kernel@...ts.infradead.org,
kbuild test robot <lkp@...el.com>,
srv_heupstream@...iatek.com, devicetree@...r.kernel.org,
Mike Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
kbuild-all@...org, Sascha Hauer <kernel@...gutronix.de>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-clk@...r.kernel.org
Subject: Re: [PATCH] clk: Move vendor's Kconfig into CCF menu section
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.
Arnd
Powered by blists - more mailing lists