From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request : u-boot-mpc85xx
Date: Wed, 21 Aug 2013 09:10:34 -0700 [thread overview]
Message-ID: <5214E67A.6080400@freescale.com> (raw)
In-Reply-To: <20130821134058.GE2644@bill-the-cat>
On 08/21/2013 06:40 AM, Tom Rini wrote:
> I see problems with:
> P1021RDB-PC_NAND BSC9132QDS_NAND_DDRCLK133 P1025RDB_NAND
> BSC9131RDB_NAND_SYSCLK100 P1022DS_SDCARD P1010RDB_NAND
> MPC8313ERDB_NAND_33 P1020RDB-PD_NAND BSC9131RDB_NAND
> P1022DS_36BIT_SDCARD P1022DS_36BIT_NAND P1022DS_36BIT_SPIFLASH
> P1022DS_NAND P1020RDB-PC_NAND P1010RDB_36BIT_NAND P1024RDB_NAND
> BSC9132QDS_NAND_DDRCLK100 P1021RDB-PC_36BIT_NAND P1022DS_SPIFLASH
> MPC8313ERDB_NAND_66 P2020RDB-PC_NAND P2020RDB-PC_36BIT_NAND
> P1020RDB-PC_36BIT_NAND
>
> The problem looks like:
> cat:
> /home/trini/work/u-boot/u-boot/powerpc/P2020RDB-PC_NAND//home/trini/work/u-boot/u-boot/powerpc/P2020RDB-PC_NAND/u-boot.bin:
> No such file or directory
>
> So something is off with separate object directories.
>
Tom,
Sorry for the trouble. One of the patch broke out-of-tree build. I will
submit a patch to fix that.
York
next prev parent reply other threads:[~2013-08-21 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 19:46 [U-Boot] Pull request : u-boot-mpc85xx York Sun
2013-08-21 13:40 ` Tom Rini
2013-08-21 16:10 ` York Sun [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-07 4:01 [U-Boot] pull request u-boot-mpc85xx Priyanka Jain
2019-11-07 17:31 ` Tom Rini
2019-11-20 5:45 ` Priyanka Jain
2019-11-20 22:43 ` Tom Rini
2019-11-26 4:49 ` Priyanka Jain
2019-12-02 15:15 ` Tom Rini
2014-01-21 23:07 [U-Boot] Pull " York Sun
2014-01-22 15:33 ` Tom Rini
2013-09-12 17:36 [U-Boot] Pull request: u-boot-mpc85xx York Sun
2013-09-14 1:26 ` Tom Rini
2013-08-21 17:28 York Sun
2013-08-22 15:18 ` Tom Rini
2013-08-14 19:11 York Sun
2013-08-16 13:35 ` Tom Rini
2013-08-12 22:43 York Sun
2013-08-13 15:38 ` Tom Rini
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=5214E67A.6080400@freescale.com \
--to=yorksun@freescale.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.