From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] Introduce table driven initializations
Date: Tue, 03 Sep 2013 12:13:32 -0600 [thread overview]
Message-ID: <522626CC.70804@wwwdotorg.org> (raw)
In-Reply-To: <1378215105-12145-1-git-send-email-pdeschrijver@nvidia.com>
On 09/03/2013 07:31 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.
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?
> 2 files changed, 455 insertions(+), 550 deletions(-)
That didn't work out as much of a line-count-reduction as I had naively
hoped. Are there any more large blocks of repetitive code left to be
converted?
prev parent reply other threads:[~2013-09-03 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 13:31 [PATCH 0/4] Introduce table driven initializations Peter De Schrijver
2013-09-03 13:31 ` [PATCH 1/4] clk: tegra: simplify periph clock data Peter De Schrijver
2013-09-03 13:31 ` [PATCH 2/4] clk: tegra: convert Tegra114 gate clocks to table Peter De Schrijver
2013-09-03 18:10 ` Stephen Warren
2013-09-03 13:31 ` [PATCH 3/4] clk: tegra114: table driven audio clock init Peter De Schrijver
2013-09-03 13:31 ` [PATCH 4/4] clk: tegra114: table driven PMC " Peter De Schrijver
2013-09-04 0:54 ` Joseph Lo
2013-09-03 13:34 ` [PATCH 0/4] Introduce table driven initializations Peter De Schrijver
2013-09-03 18:13 ` 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=522626CC.70804@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