From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
Mike Turquette <mturquette@linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
aaro.koskinen@iki.fi
Subject: Re: [GIT PULL] ARM: OMAP2: clock data migration to DT for 3.17 merge window
Date: Wed, 9 Jul 2014 08:43:52 -0700 [thread overview]
Message-ID: <20140709154352.GB28884@atomide.com> (raw)
In-Reply-To: <53B59E73.1020709@ti.com>
* Tero Kristo <t-kristo@ti.com> [140703 11:19]:
> Hi Tony,
>
> Posting this pull-request also early due to my holidays. Anyway, these
> patches were supposed to go in already during 3.16 merge window, but they
> missed it due to pending dependencies. Finalizes the move of OMAP24xx clock
> data to the DT, and also removes the legacy clock data. Might be good to try
> this branch out with n800 / 2420 hardware also as I don't have access to
> those.
>
> ---------------------------------------------------------------
>
> 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-use-dt-clks
>
> for you to fetch changes up to 6a194a6e2a8fa55e133936a124ed500aea434116:
>
> ARM: OMAP24xx: clock: remove legacy clock data (2014-07-02 15:59:03 +0300)
OK thanks pulling this into omap-for-v3.17/dt.
Tony
prev parent reply other threads:[~2014-07-09 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 18:18 [GIT PULL] ARM: OMAP2: clock data migration to DT for 3.17 merge window Tero Kristo
2014-07-09 15:43 ` Tony Lindgren [this message]
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=20140709154352.GB28884@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.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 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.