public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra: Move common clock code to arch/arm/cpu/tegra-common/clock.c
Date: Wed, 23 Jan 2013 20:54:27 -0700	[thread overview]
Message-ID: <5100B073.6000208@nvidia.com> (raw)
In-Reply-To: <1358980405-9106-1-git-send-email-twarren@nvidia.com>

On 01/23/2013 03:33 PM, Tom Warren wrote:
> This 'commonizes' much of the clock/pll code. SoC-dependent code
> and tables are left in arch/cpu/tegraXXX-common/clock.c

I think this looks OK, although the changes to the clk ID -> periph ID
mapping and validation functions and whitespace threw me initially,

Reviewed-by: Stephen Warren <swarren@nvidia.com>

> Some T30 tables needed whitespace fixes due to checkpatch complaints.

Aha, that explains it.

  reply	other threads:[~2013-01-24  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 22:33 [U-Boot] [PATCH] Tegra: Move common clock code to arch/arm/cpu/tegra-common/clock.c Tom Warren
2013-01-24  3:54 ` Stephen Warren [this message]
2013-01-24 17:59 ` Simon Glass

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=5100B073.6000208@nvidia.com \
    --to=swarren@nvidia.com \
    --cc=u-boot@lists.denx.de \
    /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