From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] : Please pull u-boot-imx -- 3 build failures
Date: Wed, 13 Mar 2013 23:26:54 +0100 [thread overview]
Message-ID: <20130313232654.3a6b2c64@lilith> (raw)
In-Reply-To: <20130313132955.09d142b5@lilith>
On Wed, 13 Mar 2013 13:29:55 +0100, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:
> Hi Stefano,
>
> On Wed, 13 Mar 2013 09:43:46 +0100, Stefano Babic <sbabic@denx.de>
> wrote:
>
> > Hi Albert,
> >
> > please pull from u-boot-imx, thanks. A question about the patch "ARM:
> > implement some Cortex-A9 errata workarounds"
> >
> > http://patchwork.ozlabs.org/patch/223419/
> >
> > I read the general agreement about it, and I have applied 2/3, because
> > this is i.MX-related. However, the effect is worthless for i.MX6 until
> > 1/3 will be applied. I read before applying that you will merge it, but
> > I have not found it in arm-tree. Do you see any problem on it ? If you
> > do not plan to apply it, it is better I revert 2/3, else the errata will
> > not be set for i.MX6.
>
> Sorry -- I should have taken 1/3 and 2/3 and haven't yet. No worries,
> though: I'll take them in, then merge your tree; you don't need to
> revert 2/3, it'll merge properly anyway.
Regardless of applying the two patches above, there is a merge conflict
between u-boot-imx/master and u-boot-arm/master between:
- commit af73034c6ba131a93ed215098f43595637ef6ac3 ("led: Use
STATUS_LED_ON and STATUS_LED_OFF when calling __led_set"), author
Otavio Salvador <otavio@ossystems.com.br>, from the IMX tree, and
- commit 4f47aceb118b291831a603d7e6ca651d76bf88e0 ("led: The gpio_led.c
code expects that LED state is from the enum"), author Holger Hans
Peter Freyther <holger@freyther.de>, from the TI tree through the ARM
tree.
Actually, both commits are functionally exactly the same, Otavio's one
being better only in that it causes smaller line widths.
I have merged the IMX tree with -Xtheirs so that the conflicts is
automatically resolved in favor of Otavio's version.
However, MAKEALL -a arm fails on three boards: nitrogen6s1g, with an
error, and nitrogen6dl2g and nitrogen6q2g, with a warning.
nitrogen6s1g:
nitrogen6x.c:89:17: error: 'CONFIG_DDR_MB' undeclared (first use in
this function)
nitrogen6x.c:89:17: note: each undeclared identifier is reported only
once for each function it appears in
nitrogen6dl2g and nitrogen6q2g:
nitrogen6x.c:89:38: warning: integer overflow in expression [-Woverflow]
These failures also happen on IMX ToT before merge. Stefano, can you
have a look? I can obviously not locate the actual faulty commit, as
support for these boards appears only in the very last commit of the IMX
branch.
> > Thanks,
> > Stefano
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-03-13 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 8:43 [U-Boot] [PULL] : Please pull u-boot-imx Stefano Babic
2013-03-13 12:29 ` Albert ARIBAUD
2013-03-13 22:26 ` Albert ARIBAUD [this message]
2013-03-13 22:36 ` [U-Boot] [PULL] : Please pull u-boot-imx -- 3 build failures Eric Nelson
2013-03-13 22:40 ` Fabio Estevam
2013-03-13 22:43 ` Eric Nelson
2013-03-13 22:44 ` Fabio Estevam
2013-03-13 22:49 ` Eric Nelson
2013-03-14 9:38 ` Stefano Babic
2013-03-14 13:48 ` Eric Nelson
2013-03-14 14:01 ` Stefano Babic
2013-03-14 7:27 ` Stefano Babic
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=20130313232654.3a6b2c64@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.