[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191023104304.GA5723@sirena.co.uk>
Date: Wed, 23 Oct 2019 11:43:04 +0100
From: Mark Brown <broonie@...nel.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Nathan Chancellor <natechancellor@...il.com>,
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 08:53:02AM +0530, Viresh Kumar wrote:
> On 22-10-19, 17:09, Nathan Chancellor wrote:
> > When building with Clang + -Wtautological-pointer-compare:
> >
> > drivers/cpufreq/s3c64xx-cpufreq.c:152:6: warning: comparison of array
> > 's3c64xx_freq_table' equal to a null pointer is always false
> > [-Wtautological-pointer-compare]
> > if (s3c64xx_freq_table == NULL) {
> > ^~~~~~~~~~~~~~~~~~ ~~~~
> > 1 warning generated.
> >
> > The definition of s3c64xx_freq_table is surrounded by an ifdef
> > directive for CONFIG_CPU_S3C6410, which is always true for this driver
> > because it depends on it in drivers/cpufreq/Kconfig.arm (and if it
> > weren't, there would be a build error because s3c64xx_freq_table would
> > not be a defined symbol).
> +broonie, who wrote this patch to see his views on why he kept it like
> this.
The driver should also have supported s3c6400 as well.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists