All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM breakage
Date: Mon, 18 Jan 2010 10:19:06 -0800	[thread overview]
Message-ID: <4B54A61A.7050907@gmail.com> (raw)
In-Reply-To: <4B5478CB.10908@windriver.com>

Tom wrote:
> After merging with u-boot/master
> Multiple targets are fixed by getenv_IPaddr
>
> However, i believe this may have broken an equal number of arm targets
> On regression testing there are multiple failures with this error
>
> smc91111_eeprom.c:33: error: redefinition of 'struct eth_device'
> make[1]: *** [ .. build/examples/standalone/smc91111_eeprom.o] Error 1
>
>   

    Hmmm... The getenv_IPaddr patch added '"#include net.h"', which
    brings this new error.  I'll come up with a workaround.

> Sample of targets
> omap3_evm
> versatile
> cerg250
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>   
regards,
Ben

  reply	other threads:[~2010-01-18 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 15:05 [U-Boot] ARM breakage Tom
2010-01-18 18:19 ` Ben Warren [this message]
2010-01-18 19:32   ` Dirk Behme

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=4B54A61A.7050907@gmail.com \
    --to=biggerbadderben@gmail.com \
    --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.