From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: linux-tegra@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>,
Joseph Lo <josephl@nvidia.com>,
Paul Walmsley <pwalmsley@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Introduce table driven initializations
Date: Wed, 04 Sep 2013 14:11:19 -0600 [thread overview]
Message-ID: <522793E7.3020000@wwwdotorg.org> (raw)
In-Reply-To: <1378304438-7780-1-git-send-email-pdeschrijver@nvidia.com>
On 09/04/2013 08:20 AM, Peter De Schrijver wrote:
> This patchset introduces a table driven initialization method for the
> audio, PMC and gate clocks. It's similar to the table we already have for
> the periph clocks.
>
> Changes since v1:
>
> * Use parent names directly in TEGRA_INIT_DATA_GATE()
For the record, I said the following in response to V1 which still applies:
I assume these patches will all go through Mike's clock tree for 3.13.
Aside from the one issue I mentioned, the series,
Acked-by: Stephen Warren <swarren@nvidia.com>
I assume this will be followed by changes to convert the Tegra20/30
clock drivers to be table-based too?
prev parent reply other threads:[~2013-09-04 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 14:20 [PATCH v2 0/4] Introduce table driven initializations Peter De Schrijver
2013-09-04 14:20 ` [PATCH v2 1/4] clk: tegra: simplify periph clock data Peter De Schrijver
2013-09-04 14:20 ` [PATCH v2 2/4] clk: tegra: convert Tegra114 gate clocks to table Peter De Schrijver
2013-09-04 14:20 ` [PATCH v2 3/4] clk: tegra114: table driven audio clock init Peter De Schrijver
2013-09-04 14:20 ` [PATCH v2 4/4] clk: tegra114: table driven PMC " Peter De Schrijver
2013-09-04 20:11 ` Stephen Warren [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=522793E7.3020000@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=josephl@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=pwalmsley@nvidia.com \
--cc=thierry.reding@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