From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 06 Jun 2012 17:19:38 -0600
Subject: [U-Boot] [PATCH v2 06/10] ARM: add tegra20 support to arm720t
In-Reply-To: <20120606221802.GK13311@nvidia.com>
References: <1338931225-12246-1-git-send-email-amartin@nvidia.com>
	<1338931225-12246-7-git-send-email-amartin@nvidia.com>
	<4FCF87DD.7080203@wwwdotorg.org>
	<20120606182545.GE13311@nvidia.com>
	<4FCFACE1.8030800@wwwdotorg.org>
	<20120606221802.GK13311@nvidia.com>
Message-ID: <4FCFE58A.9000700@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 06/06/2012 04:18 PM, Allen Martin wrote:
> On Wed, Jun 06, 2012 at 12:17:53PM -0700, Stephen Warren wrote:
>> Oh, I see. MACH_TEGRA_GENERIC means "some Tegra SoC", and CONFIG_TEGRA*
>> indicate which one. Coming from my kernel background, MACH_* is a define
>> for a particular board, and we do have a GENERIC Tegra board, so I got
>> the wrong end of the stick.
>>
>> I wonder if it's worth renaming CONFIG_MACH_TEGRA_GENERIC to
>> CONFIG_TEGRA. There don't appear to be any users of it currently.
> 
> Fine by me, maybe CONFIG_TEGRA2 should go to CONFIG_TEGRA20 also to
> keep with the new naming?

Sounds reasonable to me.