From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] build: Use filechk rules to create and update u-boot.lds
Date: Fri, 18 Apr 2014 17:02:43 -0400 [thread overview]
Message-ID: <20140418210243.GF5698@bill-the-cat> (raw)
In-Reply-To: <1397596177-10103-1-git-send-email-jon.loeliger@oracle.com>
On Tue, Apr 15, 2014 at 04:09:37PM -0500, Jon Loeliger wrote:
> Prior to this patch, the top-level linker script u-boot.lds
> used a simple $(call if_changed) check when generated.
> That mechanism misses cases where a possible include file
> change induces a change in the u-boot.lds too.
>
> This patch converts it to a stronger check using ($call filechk)
> that will also notice differences in file contents and
> will catch changes due to pre-processing as well.
>
> Signed-off-by: Jon Loeliger <jon.loeliger@oracle.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/20140418/b2ee1e97/attachment.pgp>
prev parent reply other threads:[~2014-04-18 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 21:09 [U-Boot] [PATCH] build: Use filechk rules to create and update u-boot.lds Jon Loeliger
2014-04-18 21:02 ` Tom Rini [this message]
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=20140418210243.GF5698@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