[U-Boot] [PATCH v5] nds32: Add NDS32 architecture support (header files)

[Macpaul Lin]

Hi Ming-Dien,

2010/12/14 Ming-Dien Chang <mingdien.chang at gmail.com>

> Hi, Macpual
>
> On Thu, Nov 25, 2010 at 11:12 AM, <macpaul at andestech.com> wrote:
>
> >
> > >       Is the series of patches (v1 to v5) increamental ?
> > >       Should I apply v1 first, and then v2, v3, till v5 ?
> > >       If so, what is base revision to which v1 patch is applied ?
> > >       Thanks for your help.
> > >       Morgan
> >
> > Let me explain for you, the patch version v1 to v5 just tagged for the
> > revision for the same single "patch".
> > So you just need to apply the latest patch you have. Please do not take
> > care about the v1-v4 patches.
> > The latest patch includes the latest update against to the main trunk
> > (master) source code.
> >
>
> The patch V5 includes only some  arch-depedent header files.
> Should I apply any previous patches ?
>
>
Yes, patch v5 only send the header file which the code is clean and might no
need to be modified before it has been reviewed.

Other patches will be send individually after they have be clean since the
patch might need to be revise in the future.
However, those continuous patches related to cpu core and boards which might
need be revised should not affect the "only" header file send out in v5.

If you really wan't to try the prior patches, you could try patch v4.
However, I suggest do not do that because if you develop your u-boot code
based on NDS32 patch v4,
you will have a lot of clean up work to do later. The more clean up work,
the more pain of your work and your company will be suffered. ;-p.

Otherwise, if your company doesn't want to open your u-boot's source code
nor want to be include in the u-boot main source tree.
Or you just want to try something with NDS32 "just" worked.
You can apply patch v3 or patch v4 should be  okay.

-- 
Best regards,
Macpaul Lin