From: Stephen Warren <swarren@wwwdotorg.org>
To: Danny Huang <dahuang@nvidia.com>
Cc: linux@arm.linux.org.uk, ldewangan@nvidia.com, olof@lixom.net,
hdoyu@nvidia.com, thierry.reding@avionic-design.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4] ARM: tegra: expose chip ID and revision
Date: Fri, 15 Mar 2013 13:16:56 -0600 [thread overview]
Message-ID: <514373A8.2080807@wwwdotorg.org> (raw)
In-Reply-To: <1363222120-22210-1-git-send-email-dahuang@nvidia.com>
On 03/13/2013 06:48 PM, Danny Huang wrote:
> Expose Tegra chip ID and revision in /sys/devices/soc for user mode
> usage
Applied to Tegra's for-3.10/soc branch.
prev parent reply other threads:[~2013-03-15 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 0:48 [PATCH v4] ARM: tegra: expose chip ID and revision Danny Huang
2013-03-15 19:16 ` 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=514373A8.2080807@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=dahuang@nvidia.com \
--cc=hdoyu@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=thierry.reding@avionic-design.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