From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/3] ARM: tegra: add speedo identification for T20/T30
Date: Thu, 15 Nov 2012 14:40:13 -0700 [thread overview]
Message-ID: <50A5613D.5080601@wwwdotorg.org> (raw)
In-Reply-To: <1352965354-650-1-git-send-email-dahuang@nvidia.com>
On 11/15/2012 12:42 AM, Danny Huang wrote:
> This patch series adds speedo identification functionality for tegra
> T20 and T30. It reads speedo value from fuse and chooses CPU and core
> process ID by checking speedo corner tables.
I think this all looks fine; I assume there will be some forthcoming
usage of the new variables.
I applied the series with some very minor changes to the printfs and
commit description to that "Tegra20" was consistently used instead of
"T20" or "Tegra2", and the same for Tegra30.
prev parent reply other threads:[~2012-11-15 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 7:42 [PATCH V2 0/3] ARM: tegra: add speedo identification for T20/T30 Danny Huang
2012-11-15 7:42 ` [PATCH V2 1/3] ARM: tegra: flexible spare fuse read function Danny Huang
2012-11-15 7:42 ` [PATCH V2 2/3] ARM: tegra: Add speedo-based process identification Danny Huang
2012-11-15 7:42 ` [PATCH V2 3/3] ARM: tegra: T30 " Danny Huang
2012-11-15 21:40 ` 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=50A5613D.5080601@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).