From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Heiko Stübner'" <heiko@sntech.de>,
"'Tomasz Figa'" <tomasz.figa@gmail.com>
Cc: 'Sergei Shtylyov' <sergei.shtylyov@cogentembedded.com>,
t.figa@samsung.com, linux-samsung-soc@vger.kernel.org,
mturquette@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH v2 1/9] ARM: S3C24XX: cpufreq-utils: don't write raw values to MPLLCON when using ccf
Date: Tue, 06 May 2014 13:27:58 +0900 [thread overview]
Message-ID: <0e4501cf68e3$8f6612d0$ae323870$@samsung.com> (raw)
In-Reply-To: <1538030.0aVnFA3MgQ@phil>
Heiko Stübner wrote:
>
[...]
> > Anyway, Heiko, thanks for working on this. I'll try to review rest of
> > the series soon. (I'm attending the ELC next week, though, so I'm not
> > sure if I find some time then, though.)
>
Yeah, this series is really good to us.
> Just as a reminder, there isn't this much to still review, as you
> Acked/Reviewed most of the series in v1 and only this patch as well as 2
> and 5
> still need a review/ack - and the only changes are fixes for your
> comments ;-)
>
I think so. Since I will apply this series in this week, if any big
comments, please let us know.
Heiko, thanks for the v2.1 as well.
- Kukjin
next prev parent reply other threads:[~2014-05-06 4:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 19:32 [PATCH v2 0/9] ARM: S3C24XX: convert s3c2410, s3c2440 s3c2442 to common clock framework Heiko Stübner
2014-04-23 19:34 ` [PATCH v2 1/9] ARM: S3C24XX: cpufreq-utils: don't write raw values to MPLLCON when using ccf Heiko Stübner
2014-04-23 20:42 ` Sergei Shtylyov
2014-04-23 20:55 ` Tomasz Figa
2014-04-23 21:11 ` Heiko Stübner
2014-05-06 4:27 ` Kukjin Kim [this message]
2014-05-06 15:07 ` Tomasz Figa
2014-05-08 17:36 ` Tomasz Figa
2014-04-23 21:02 ` Sergei Shtylyov
2014-04-23 22:08 ` [PATCH v2.1 " Heiko Stübner
2014-04-23 19:34 ` [PATCH v2 2/9] clk: samsung: add clock driver for external clock outputs Heiko Stübner
2014-04-23 19:35 ` [PATCH v2 3/9] ARM: S3C24XX: enable usage of common dclk if common clock framework is enabled Heiko Stübner
2014-04-23 20:09 ` [PATCH v2.1 " Heiko Stübner
2014-05-09 16:49 ` Paul Bolle
2014-05-09 17:53 ` Tomasz Figa
2014-05-09 23:07 ` Heiko Stübner
2014-05-09 23:11 ` Tomasz Figa
2014-05-09 23:33 ` Heiko Stübner
2014-05-12 22:47 ` Kukjin Kim
2014-05-12 22:57 ` Heiko Stübner
2014-05-09 22:57 ` Heiko Stübner
2014-04-23 19:36 ` [PATCH v2 4/9] dt-bindings: add documentation for s3c2410 clock controller Heiko Stübner
2014-05-06 15:19 ` [ATTN] " Tomasz Figa
2014-04-23 19:36 ` [PATCH v2 5/9] clk: samsung: add clock controller driver for s3c2410, s3c2440 and s3c2442 Heiko Stübner
2014-04-23 19:37 ` [PATCH v2 6/9] ARM: S3C24XX: add platform code for conversion to the common clock framework Heiko Stübner
2014-04-23 19:37 ` [PATCH v2 7/9] ARM: S3C24XX: convert s3c2440 and s3c2442 to " Heiko Stübner
2014-04-23 19:38 ` [PATCH v2 8/9] ARM: S3C24XX: convert s3c2410 " Heiko Stübner
2014-04-23 20:10 ` [PATCH v2.1 " Heiko Stübner
2014-04-23 19:38 ` [PATCH v2 9/9] ARM: S3C24XX: remove legacy clock code Heiko Stübner
2014-04-23 20:11 ` [PATCH v2.1 " Heiko Stübner
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='0e4501cf68e3$8f6612d0$ae323870$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=t.figa@samsung.com \
--cc=tomasz.figa@gmail.com \
/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