From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 3/4] config.mk: specify the exact path to standalone linker script
Date: Fri, 7 Mar 2014 17:29:24 -0500 [thread overview]
Message-ID: <20140307222924.GS16805@bill-the-cat> (raw)
In-Reply-To: <1394006380-14192-4-git-send-email-yamada.m@jp.panasonic.com>
On Wed, Mar 05, 2014 at 04:59:39PM +0900, Masahiro Yamada wrote:
> We want to change the build system to include config.mk
> only from ./Makefile and spl/Makefile.
> We must prepare for that in this commit.
>
> $(src) is a moving target and not handy for our purpose.
> We must replace it with a fixed path.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140307/6ca4348b/attachment.pgp>
next prev parent reply other threads:[~2014-03-07 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 7:59 [U-Boot] [PATCH v3 0/4] Big acceleration of Kbuild performance Masahiro Yamada
2014-03-05 7:59 ` [U-Boot] [PATCH v3 1/4] kbuild, blackfin: Add CONFIG_CC_OPTIMIZE_LIBS_FOR_SPEED Masahiro Yamada
2014-03-07 22:13 ` Simon Glass
2014-03-07 22:29 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-03-05 7:59 ` [U-Boot] [PATCH v3 2/4] kbuild: add CONFIG_ prefix to USE_PRIVATE_LIBGCC Masahiro Yamada
2014-03-07 22:15 ` Simon Glass
2014-03-07 22:29 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-03-05 7:59 ` [U-Boot] [PATCH v3 3/4] config.mk: specify the exact path to standalone linker script Masahiro Yamada
2014-03-07 22:17 ` Simon Glass
2014-03-07 22:29 ` Tom Rini [this message]
2014-03-05 7:59 ` [U-Boot] [PATCH v3 4/4] kbuild: improve Kbuild speed Masahiro Yamada
2014-03-07 22:29 ` [U-Boot] [U-Boot,v3,4/4] " 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=20140307222924.GS16805@bill-the-cat \
--to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox