[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191023165923.GL5723@sirena.co.uk>
Date: Wed, 23 Oct 2019 17:59:23 +0100
From: Mark Brown <broonie@...nel.org>
To: Nathan Chancellor <natechancellor@...il.com>
Cc: Viresh Kumar <viresh.kumar@...aro.org>,
Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, clang-built-linux@...glegroups.com
Subject: Re: [PATCH] cpufreq: s3c64xx: Remove pointless NULL check in
s3c64xx_cpufreq_driver_init
On Wed, Oct 23, 2019 at 09:54:17AM -0700, Nathan Chancellor wrote:
> On Wed, Oct 23, 2019 at 05:36:56PM +0100, Mark Brown wrote:
> > On Wed, Oct 23, 2019 at 09:26:28AM -0700, Nathan Chancellor wrote:
> > > On Wed, Oct 23, 2019 at 11:43:04AM +0100, Mark Brown wrote:
> > > > The driver should also have supported s3c6400 as well.
> > > Kconfig says otherwise, unless I am missing something.
> > Note the XX in the config option.
> But what about the depends and the help text?
Viresh asked why the driver was written with s3c6410 support optional.
I explained that the reason that it was written this way was to
accomodate s3c6400 support.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists