From: Arnd Bergmann <arnd@arndb.de>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
cpufreq@vger.kernel.org, Tomasz Figa <t.figa@samsung.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Kukjin Kim <kgene.kim@samsung.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
'linux-arm-kernel' <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] cpufreq: exynos: allow disabling cpufreq drivers
Date: Fri, 19 Apr 2013 20:59:38 +0200 [thread overview]
Message-ID: <201304192059.38606.arnd@arndb.de> (raw)
In-Reply-To: <51717623.2060709@samsung.com>
On Friday 19 April 2013, Sylwester Nawrocki wrote:
> Not sure what happened here, but my and Tomasz's Tested-by were given
> for v5 of the patch series including 6e6aac7590, while it seems v6
> has been applied. And the patch is not same in both series.
I see.
> There could be some differences in the base tree I used when testing
> this [1] series, as it was hard to determine against what tag it was
> created exactly. Also I didn't test in on all platforms, only
> Exynos4412.
Maybe you just didn't have CPUFREQ enabled? I also didn't notice this
bug at first because it is turned off in the defconfigs.
It could also be working by chance on EXYNOS4, since the register
definitions were not actually removed from the regs-clk.h header
for those.
Arnd
next prev parent reply other threads:[~2013-04-19 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 13:54 [PATCH] cpufreq: exynos: allow disabling cpufreq drivers Arnd Bergmann
2013-04-19 14:33 ` Arnd Bergmann
2013-04-19 16:51 ` Sylwester Nawrocki
2013-04-19 18:59 ` Arnd Bergmann [this message]
2013-04-19 20:37 ` Sylwester Nawrocki
2013-04-19 20:43 ` Arnd Bergmann
2013-04-19 21:12 ` Sylwester Nawrocki
2013-04-19 21:10 ` [PATCH] ARM: exynos: restore mach/regs-clock.h for exynos5 Arnd Bergmann
2013-04-19 21:17 ` Olof Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201304192059.38606.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cpufreq@vger.kernel.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=s.nawrocki@samsung.com \
--cc=t.figa@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox