From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
Mike Turquette <mturquette@linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] ARM: OMAP2+: clock cleanup for v3.17 merge window
Date: Fri, 4 Jul 2014 10:02:33 +0300 [thread overview]
Message-ID: <53B65189.4070807@ti.com> (raw)
In-Reply-To: <20140704064813.GA28884@atomide.com>
On 07/04/2014 09:48 AM, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [140703 11:10]:
>> Hi Tony,
>>
>> Posting this early, as I will be going for vacation from next week and might
>> miss the merge window myself. Small cleanup set for the clock drivers
>> residing under mach-omap2 folder to prepare their move under drivers/clk.
>> I'll leave it for your judgement whether you pull this or not based on the
>> potential feedback.
>>
>> ----------------------------------------------------------------
>>
>> The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
>>
>> Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
>>
>> are available in the git repository at:
>>
>> git@github.com:t-kristo/linux-pm.git for-v3.17/omap2-clk-cleanup
>>
>> for you to fetch changes up to 4eccc64a2bc25514754c30cdfc985207aee8b2fd:
>>
>> ARM: OMAP2+: clock/interface: remove some headers from clkt_iclk.c file
>> (2014-07-01 17:46:27 +0300)
>
> This would be best queued by Paul if OK. I'm assuming all these
> pull requests are independet of each other, right?
Yea this is fine with me. All the pull-requests are independent.
-Tero
>
> Regards,
>
> Tony
>
>
>> ----------------------------------------------------------------
>> Tero Kristo (13):
>> ARM: OMAP2+: clock/dpll: fix _dpll_test_fint arithmetics overflow
>> ARM: OMAP4+: clock: remove DEFINE_CLK_OMAP_HSDIVIDER macro
>> ARM: OMAP4+: dpll: remove cpu_is_omap44xx checks
>> ARM: OMAP4+: dpll44xx: remove cm-regbits-44xx.h and clock44xx.h
>> includes
>> ARM: OMAP2+: clock: introduce ti_clk_features flags
>> ARM: OMAP2+: clock: add fint values to the ti_clk_features struct
>> ARM: OMAP2+: clock/dpll: add private API for checking if DPLL is in
>> bypass
>> ARM: OMAP2+: clock/dpll: convert bypass check to use clk_features
>> ARM: OMAP2+: clock/dpll: add jitter correction behind clk_features
>> ARM: OMAP2+: clock/interface: add a clk_features definition for idlest
>> value
>> ARM: OMAP2+: clock/dpll: remove unused header includes from
>> clkt_dpll.c
>> ARM: OMAP2+: clock/dpll: remove unused header includes from dpll3xxx.c
>> ARM: OMAP2+: clock/interface: remove some headers from clkt_iclk.c
>> file
>>
>> arch/arm/mach-omap2/clkt_dpll.c | 100
>> ++++++++++++++++++---------------------
>> arch/arm/mach-omap2/clkt_iclk.c | 8 ++--
>> arch/arm/mach-omap2/clock.c | 76 ++++++++++++++++++++++++++---
>> arch/arm/mach-omap2/clock.h | 44 ++++++++---------
>> arch/arm/mach-omap2/dpll3xxx.c | 7 +--
>> arch/arm/mach-omap2/dpll44xx.c | 19 +++++---
>> arch/arm/mach-omap2/io.c | 2 +
>> 7 files changed, 155 insertions(+), 101 deletions(-)
next prev parent reply other threads:[~2014-07-04 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 18:09 [GIT PULL] ARM: OMAP2+: clock cleanup for v3.17 merge window Tero Kristo
2014-07-04 6:48 ` Tony Lindgren
2014-07-04 7:02 ` Tero Kristo [this message]
2014-07-04 7:04 ` Tony Lindgren
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=53B65189.4070807@ti.com \
--to=t-kristo@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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