All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Thomas Abraham <thomas.ab@samsung.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Kukjin Kim <kgene.kim@samsung.com>, Kukjin Kim <kgene@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Lukasz Majewski <l.majewski@samsung.com>,
	Heiko Stuebner <heiko@sntech.de>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Kevin Hilman <khilman@linaro.org>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] cpufreq: exynos: remove Exynos5250 specific cpufreq driver support
Date: Wed, 01 Jul 2015 15:26:57 +0200	[thread overview]
Message-ID: <3020078.iPsxHyMrL0@amdc1976> (raw)
In-Reply-To: <5591E12E.7060007@samsung.com>


Hi,

On Tuesday, June 30, 2015 09:22:06 AM Krzysztof Kozlowski wrote:
> On 30.06.2015 02:26, Bartlomiej Zolnierkiewicz wrote:
> > Exynos5250 based platforms have switched over to use generic
> > cpufreq driver for cpufreq functionality. So the Exynos
> > specific cpufreq support for these platforms can be removed.
> > 
> > Based on the earlier work by Thomas Abraham.
> > 
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> > Cc: Thomas Abraham <thomas.ab@samsung.com>
> > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > ---
> >  drivers/cpufreq/Kconfig.arm          |  11 --
> >  drivers/cpufreq/Makefile             |   1 -
> >  drivers/cpufreq/exynos-cpufreq.c     |   3 -
> >  drivers/cpufreq/exynos-cpufreq.h     |  17 ---
> >  drivers/cpufreq/exynos5250-cpufreq.c | 210 -----------------------------------
> >  5 files changed, 242 deletions(-)
> >  delete mode 100644 drivers/cpufreq/exynos5250-cpufreq.c
> 
> Nice diff stat, I like it!
> 
> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> 
> Few thoughts:
> 1. Javier's email has changed, CC-ed the correct one. Can you update it
> in all patches (CC-tags)?

Done in v3.

> 2. It looks like the patchset should go through one tree so the
> Exynos5250 cpufreq support won't disappear, right?

Right, this would be an ideal situation.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

WARNING: multiple messages have this Message-ID (diff)
From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] cpufreq: exynos: remove Exynos5250 specific cpufreq driver support
Date: Wed, 01 Jul 2015 15:26:57 +0200	[thread overview]
Message-ID: <3020078.iPsxHyMrL0@amdc1976> (raw)
In-Reply-To: <5591E12E.7060007@samsung.com>


Hi,

On Tuesday, June 30, 2015 09:22:06 AM Krzysztof Kozlowski wrote:
> On 30.06.2015 02:26, Bartlomiej Zolnierkiewicz wrote:
> > Exynos5250 based platforms have switched over to use generic
> > cpufreq driver for cpufreq functionality. So the Exynos
> > specific cpufreq support for these platforms can be removed.
> > 
> > Based on the earlier work by Thomas Abraham.
> > 
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> > Cc: Thomas Abraham <thomas.ab@samsung.com>
> > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > ---
> >  drivers/cpufreq/Kconfig.arm          |  11 --
> >  drivers/cpufreq/Makefile             |   1 -
> >  drivers/cpufreq/exynos-cpufreq.c     |   3 -
> >  drivers/cpufreq/exynos-cpufreq.h     |  17 ---
> >  drivers/cpufreq/exynos5250-cpufreq.c | 210 -----------------------------------
> >  5 files changed, 242 deletions(-)
> >  delete mode 100644 drivers/cpufreq/exynos5250-cpufreq.c
> 
> Nice diff stat, I like it!
> 
> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> 
> Few thoughts:
> 1. Javier's email has changed, CC-ed the correct one. Can you update it
> in all patches (CC-tags)?

Done in v3.

> 2. It looks like the patchset should go through one tree so the
> Exynos5250 cpufreq support won't disappear, right?

Right, this would be an ideal situation.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

  reply	other threads:[~2015-07-01 13:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 17:26 [PATCH v2 0/4] cpufreq: use generic cpufreq drivers for Exynos5250 platform Bartlomiej Zolnierkiewicz
2015-06-29 17:26 ` Bartlomiej Zolnierkiewicz
2015-06-29 17:26 ` [PATCH v2 1/4] clk: samsung: exynos5250: add cpu clock configuration data and instantiate cpu clock Bartlomiej Zolnierkiewicz
2015-06-29 17:26   ` Bartlomiej Zolnierkiewicz
2015-06-29 17:26 ` [PATCH v2 2/4] ARM: dts: Exynos5250: add CPU OPP and regulator supply property Bartlomiej Zolnierkiewicz
2015-06-29 17:26   ` Bartlomiej Zolnierkiewicz
2015-06-30  0:13   ` Krzysztof Kozlowski
2015-06-30  0:13     ` Krzysztof Kozlowski
2015-06-29 17:26 ` [PATCH v2 3/4] ARM: Exynos: switch to using generic cpufreq driver for Exynos5250 Bartlomiej Zolnierkiewicz
2015-06-29 17:26   ` Bartlomiej Zolnierkiewicz
2015-06-30  0:16   ` Krzysztof Kozlowski
2015-06-30  0:16     ` Krzysztof Kozlowski
2015-06-29 17:26 ` [PATCH v2 4/4] cpufreq: exynos: remove Exynos5250 specific cpufreq driver support Bartlomiej Zolnierkiewicz
2015-06-29 17:26   ` Bartlomiej Zolnierkiewicz
2015-06-30  0:22   ` Krzysztof Kozlowski
2015-06-30  0:22     ` Krzysztof Kozlowski
2015-07-01 13:26     ` Bartlomiej Zolnierkiewicz [this message]
2015-07-01 13:26       ` 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=3020078.iPsxHyMrL0@amdc1976 \
    --to=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=javier@dowhile0.org \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kgene@kernel.org \
    --cc=khilman@linaro.org \
    --cc=l.majewski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=s.nawrocki@samsung.com \
    --cc=thomas.ab@samsung.com \
    --cc=tomasz.figa@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.