[U-Boot] [PATCH] arm: Tegra: Fix Harmony and Ventana builds

[Tom Warren]

Sorry, folks. Please ignore u-boot-tegra/next for now. It's in transition.

u-boot-tegra/master has some new patches (getting ready for a pull request) that changed the Seaboard Makefile but not the Harmony or Ventana ones. The fix-it patch I submitted should've had a line that said it applies against u-boot-tegra/master (which really should be 'next', I guess).

The BUG= and TEST= lines are required for ChromeOS U-Boot submissions - I just got into the habit of always applying them to commit messages. I'll remove 'em, add some more info about where exactly this patch applies, and resubmit.

Thanks for catching all this,

Tom

> -----Original Message-----
> From: Albert ARIBAUD [mailto:albert.u.boot at aribaud.net]
> Sent: Monday, December 19, 2011 11:56 PM
> To: Stephen Warren
> Cc: Tom Warren; u-boot at lists.denx.de; sjg at chromium.org; wd at denx.de; Tom
> Warren
> Subject: Re: [PATCH] arm: Tegra: Fix Harmony and Ventana builds
> 
> Hi all,
> 
> Le 20/12/2011 01:06, Stephen Warren a écrit :
> > Tom Warren wrote at Monday, December 19, 2011 4:09 PM:
> >> Signed-off-by: Tom Warren<twarren at nvidia.com>
> >>
> >> BUG=none
> >> TEST=built all 3 (Harmony, Seaboard and Ventana) and tested Seaboard
> >
> > Tom,
> >
> > I'm a little confused by this. The patch removes ../common/board.o
> > from COBJS for Harmony and Ventana, but not from Seaboard, and at
> > least in u-boot-tegra/ next, Seaboard still references that file.
> >
> > Also, applying this patch causes Harmony and Ventana to fail to build
> > (link) due to undefined symbols typically provided by common/board.o.
> >
> > What branch is the patch targeted at, and what build problems is it
> > solving?
> 
> Plus, I would suggest making the commit message less cryptic; I can make no
> heads or tails of these "BUG=" and "TEST=" lines.
> 
> Amicalement,
> --
> Albert.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------