From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
Date: Wed, 3 Feb 2016 13:20:02 +0100
Subject: [U-Boot] [PATCH 3/5] kbuild: use $(call cmd,
 ) rather than $(call if_changed, ) where possible
In-Reply-To: <20160203131835.0bdba82e@lilith>
References: <1454501114-4346-1-git-send-email-yamada.masahiro@socionext.com>
 <1454501114-4346-4-git-send-email-yamada.masahiro@socionext.com>
 <20160203131835.0bdba82e@lilith>
Message-ID: <20160203132002.20d6f525@lilith>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.