From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/6] ARM: tegra20: Separate out clk ops and clk data
Date: Thu, 28 Jun 2012 11:37:35 -0600 [thread overview]
Message-ID: <4FEC965F.4060104@wwwdotorg.org> (raw)
In-Reply-To: <1340879846-12900-3-git-send-email-pgaikwad@nvidia.com>
On 06/28/2012 04:37 AM, Prashant Gaikwad wrote:
> Move clock initialization data to separate file. This is
> required for migrating to generic clock framework if static
> initialization is used.
>
> TODO: Add clock suspend/resume support
Is the suspend/resume code something that was present in the existing
Tegra clock code? If not, I'd be tempted to just drop that TODO line
from the patch description when applying this.
next prev parent reply other threads:[~2012-06-28 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 10:37 [PATCH 0/6] Port Tegra to generic clk framework Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 1/6] ARM: tegra30: Separate out clk ops and clk data Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 2/6] ARM: tegra20: " Prashant Gaikwad
2012-06-28 17:37 ` Stephen Warren [this message]
2012-06-29 2:06 ` Prashant G
2012-06-28 10:37 ` [PATCH 3/6] ARM: tegra: Rename tegra20 clock file Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 4/6] ARM: tegra: Add clk_tegra structure and helper functions Prashant Gaikwad
2012-06-28 18:28 ` Mike Turquette
2012-06-29 8:34 ` Prashant Gaikwad
2012-07-03 0:09 ` Turquette, Mike
2012-07-03 1:31 ` Stephen Warren
2012-07-03 1:49 ` Turquette, Mike
2012-06-28 10:37 ` [PATCH 5/6] ARM: tegra: Port tegra to generic clock framework Prashant Gaikwad
2012-06-28 17:29 ` Prashant G
2012-06-28 10:37 ` [PATCH 6/6] ARM: tegra: Remove duplicate code Prashant Gaikwad
2012-06-28 17:39 ` [PATCH 0/6] Port Tegra to generic clk framework Stephen Warren
2012-06-29 17:24 ` Stephen Warren
2012-07-02 18:12 ` Stephen Warren
2012-07-03 11:29 ` Prashant Gaikwad
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=4FEC965F.4060104@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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