[U-Boot] [PATCH v2] OMAP3: Remove legacy NAND defines

[Dirk Behme <dirk.behme@googlemail.com>]

Dear Jean-Christophe,

Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 10:21 Mon 20 Apr     , Scott Wood wrote:
>> On Mon, Apr 20, 2009 at 07:19:57AM +0200, Wolfgang Denk wrote:
>>> Dear Jean-Christophe PLAGNIOL-VILLARD,
>>>
>>> In message <20090417053017.GD31923@game.jcrosoft.org> you wrote:
>>>> On 20:15 Tue 14 Apr     , Dirk Behme wrote:
>>>>> Remove remaining legacy NAND defines for Beagle, EVM, Overo and Pandora.
>>>>>
>>>>> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
>>>>> ---
>>>>>
>>>>> For Zoom1 it was already removed by
>>>>>
>>>>> http://lists.denx.de/pipermail/u-boot/2009-April/050150.html
>>>>> http://lists.denx.de/pipermail/u-boot/2009-April/050871.html
>>>>>
>>>>> Changes in v2:
>>>>>
>>>>> - Remove even more legacy NAND defines. Thanks to Tom Rix for the hint.
>>>>>
>>>>> This version v2 makes all previous versions of this patch obsolete. 
>>>> will be apply on the next
>>> Why "next" ? As I understand, this fixes build problems in the
>>> *current* tree?
>> I don't think so -- my understanding is that these boards aren't
>> currently using legacy NAND; they just have some remnants of it that need
>> cleaning out.
> correct
> 
> as it's cosmetics change I've not in mind to apply them for the release but
> the next

Independent where it will be applied, it would be nice if you would do 
it *consistent*.

Same changes for Zoom1

http://lists.denx.de/pipermail/u-boot/2009-April/050159.html

were applied to current.

It's my understanding that 'next' is for preparation of new features 
to be merged next merge window? This is no new feature. It's even no 
bug fix. It's just removal of dead, unused marcos. So IMHO should be 
fine to be merged while -rc?

Where can I see 'next' in gitweb, btw?

Dirk