From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] kbuild: use $(call cmd, ) rather than $(call if_changed, ) where possible
Date: Wed, 3 Feb 2016 13:20:02 +0100 [thread overview]
Message-ID: <20160203132002.20d6f525@lilith> (raw)
In-Reply-To: <20160203131835.0bdba82e@lilith>
Hello Albert,
On Wed, 3 Feb 2016 13:18:35 +0100, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:
> Hello Masahiro,
>
> On Wed, 3 Feb 2016 21:05:12 +0900, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
> > These build commands are constant (mostly, just concatenating images,
> > or just copying). No need to use $(call if_changed,...) for them.
>
> I am a total kbuild ignorant, so I'm probably asking a stupid question,
> but hey.
>
> What are the exact semantics of $(call if_changed,)? I thought it meant
> "call the function if any of the dependencies has changed. If it does,
> then won't this patch make the corresponding action systematic, causing
> unneeded concatenations or copies?
NVM, the answer could be found in later patches in the series.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2016-02-03 12:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 12:05 [U-Boot] [PATCH 0/5] kbuild fixes Masahiro Yamada
2016-02-03 12:05 ` [U-Boot] [PATCH 1/5] kbuild: remove unneeded ifdef conditionals around build rules Masahiro Yamada
2016-02-03 12:05 ` [U-Boot] [PATCH 2/5] kbuild: sunxi: fix build rule of sunxi-spl.bin Masahiro Yamada
2016-02-03 12:05 ` [U-Boot] [PATCH 3/5] kbuild: use $(call cmd, ) rather than $(call if_changed, ) where possible Masahiro Yamada
2016-02-03 12:18 ` Albert ARIBAUD
2016-02-03 12:20 ` Albert ARIBAUD [this message]
2016-02-03 15:57 ` Stephen Warren
2016-02-05 5:33 ` Masahiro Yamada
2016-02-05 8:11 ` Ian Campbell
2016-02-03 12:05 ` [U-Boot] [PATCH 4/5] kbuild: add missing FORCE where $(call if_changed, ) is used Masahiro Yamada
2016-02-03 12:05 ` [U-Boot] [PATCH 5/5] kbuild: fix build rule of u-boot-spl.dtb Masahiro Yamada
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=20160203132002.20d6f525@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox