From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Bryan Wu <pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 2/2] ARM: DT: tegra: Unify the description of Tegra20 boards
Date: Wed, 02 Jan 2013 12:33:58 -0700 [thread overview]
Message-ID: <50E48BA6.6080106@wwwdotorg.org> (raw)
In-Reply-To: <1356032489-27619-2-git-send-email-pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 12/20/2012 12:41 PM, Bryan Wu wrote:
> Use engineering name 'Tegra20' instead of 'Tegra2'
I have applied just patch 2/2 to Tegra's for-3.9/dt branch. I'll wait
for an updated patch 1/2 that documents the board-level compatible property.
next prev parent reply other threads:[~2013-01-02 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 19:41 [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support Bryan Wu
[not found] ` <1356032489-27619-1-git-send-email-pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-20 19:41 ` [PATCH 2/2] ARM: DT: tegra: Unify the description of Tegra20 boards Bryan Wu
[not found] ` <1356032489-27619-2-git-send-email-pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-02 19:33 ` Stephen Warren [this message]
2012-12-20 19:58 ` [PATCH 1/2] ARM: DT: tegra: Add Tegra30 Beaver board support Stephen Warren
2012-12-28 16:22 ` Rob Herring
[not found] ` <50DDC743.2080606-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-28 23:54 ` Stephen Warren
[not found] ` <50DE3146.6090001-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-29 4:43 ` Olof Johansson
[not found] ` <CAOesGMgW890K4Wo2-SFE4YFn5f8T950BTZ82rkCQfwpV+bsRyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-02 18:13 ` Peng Wu
[not found] ` <50E478AF.2040406-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-08 21:40 ` Grant Likely
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=50E48BA6.6080106@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pengw-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).