From: Kukjin Kim <kgene@kernel.org>
To: "'Bartlomiej Zolnierkiewicz'" <b.zolnierkie@samsung.com>,
"'Viresh Kumar'" <viresh.kumar@linaro.org>
Cc: "'linux-samsung-soc'" <linux-samsung-soc@vger.kernel.org>,
"'Kukjin Kim'" <kgene@kernel.org>,
"'Arnd Bergmann'" <arnd@arndb.de>,
"'Eduardo Valentin'" <edubezval@gmail.com>,
"'Lukasz Majewski'" <l.majewski@samsung.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] cpufreq: exynos: allow build for !THERMAL or !CPU_THERMAL cases
Date: Tue, 24 Mar 2015 21:53:49 +0900 [thread overview]
Message-ID: <02c201d06631$92a06440$b7e12cc0$@kernel.org> (raw)
In-Reply-To: <75115513.B5dLcdQ7nU@amdc1032>
Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
Hi,
> On Monday, February 23, 2015 10:07:50 AM Viresh Kumar wrote:
> > On 20 February 2015 at 21:50, Bartlomiej Zolnierkiewicz
> > <b.zolnierkie@samsung.com> wrote:
> > > Allow driver build for !THERMAL or !CPU_THERMAL cases.
> > >
> > > The new dependency rule is the same as the one that CPUFREQ_DT
> > > option has (for cpufreq-dt driver which has the same issue with
> > > using of_cpufreq_cooling_register()).
> > >
> > > Cc: Kukjin Kim <kgene@kernel.org>
Looks OK to me,
Acked-by: Kukjin Kim <kgene@kernel.org>
Thanks,
Kukjin
> > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > Cc: Eduardo Valentin <edubezval@gmail.com>
> > > Cc: Lukasz Majewski <l.majewski@samsung.com>
> > > Fixes: 8b2b4a4e5366 ("cpufreq: exynos: allow modular build")
> > > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > > ---
> > > drivers/cpufreq/Kconfig.arm | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> > > index 1b06fc4..f4df4af3 100644
> > > --- a/drivers/cpufreq/Kconfig.arm
> > > +++ b/drivers/cpufreq/Kconfig.arm
> > > @@ -28,7 +28,8 @@ config ARM_VEXPRESS_SPC_CPUFREQ
> > > config ARM_EXYNOS_CPUFREQ
> > > tristate "SAMSUNG EXYNOS CPUfreq Driver"
> > > depends on CPU_EXYNOS4210 || SOC_EXYNOS4212 || SOC_EXYNOS4412 || SOC_EXYNOS5250
> > > - depends on THERMAL
> > > + # if CPU_THERMAL is on and THERMAL=m, ARM_EXYNOS_CPUFREQ cannot be =y:
> > > + depends on !CPU_THERMAL || THERMAL
> > > help
> > > This adds the CPUFreq driver for Samsung EXYNOS platforms.
> > > Supported SoC versions are:
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Thank you for the ACK.
>
> Would you pick this patch up or should I resend it to Rafael?
>
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
next prev parent reply other threads:[~2015-03-24 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 16:20 [PATCH] cpufreq: exynos: allow build for !THERMAL or !CPU_THERMAL cases Bartlomiej Zolnierkiewicz
2015-02-23 4:37 ` Viresh Kumar
2015-03-23 16:43 ` Bartlomiej Zolnierkiewicz
2015-03-24 2:25 ` Viresh Kumar
2015-03-24 12:53 ` Kukjin Kim [this message]
2015-03-24 14:53 ` Eduardo Valentin
-- strict thread matches above, loose matches on Subject: below --
2015-03-24 11:33 Bartlomiej Zolnierkiewicz
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='02c201d06631$92a06440$b7e12cc0$@kernel.org' \
--to=kgene@kernel.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=edubezval@gmail.com \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).