From: Jason Cooper <jason@lakedaemon.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Linus Torvalds <torvalds@linux-foundation.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <rob.herring@linaro.org>
Subject: Re: [git pull] Devicetree changes for v3.15
Date: Fri, 26 Sep 2014 10:19:43 -0400 [thread overview]
Message-ID: <20140926141943.GC23926@titan.lakedaemon.net> (raw)
In-Reply-To: <CACRpkdZoo=P7uTO1rNDD_HUPjfAk26C0=mNYPoZmTV0wcO3V-w@mail.gmail.com>
Linus,
On Fri, Sep 26, 2014 at 02:30:53PM +0200, Linus Walleij wrote:
> On Tue, Apr 1, 2014 at 12:15 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> > Here are the dt changes I've got queued up for v3.15. The full
> > description is below in the tag. Please pull.
> (...)
> > Jason Cooper (1):
> > kbuild: dtbs_install: new make target
Exact patch is:
f4d4ffc03efc kbuild: dtbs_install: new make target
> After this patch a while back I have observed the following behaviour
> of the kernel build:
>
> make zImage
> make zImage
> -> incremental build, just relink
>
> make zImage
> make dtbs
> make zImage
> -> The whole kernel gets rebuilt
>
> So now if I happen to recompile my device trees, I suddenly want
> the entire zImage to be rebuilt to? It's by definition not changes that
> affect the kernel build :-(
>
> I noticed this because my build scripts calls make dtbs && make zImage,
> and started to rebuild absolutely everything all the time.
>
> Do you think this can be fixed? It's quite simple to reproduce...
Does the attached fix your problem?
thx,
Jason.
----------->8------------------------------------------
diff --git a/arch/arm/Makefile b/arch/arm/Makefile
index 0ce9d0f71f2a..a88b13af58d2 100644
--- a/arch/arm/Makefile
+++ b/arch/arm/Makefile
@@ -313,7 +313,9 @@ $(INSTALL_TARGETS):
$(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
PHONY += dtbs dtbs_install
-dtbs dtbs_install: prepare scripts
+dtbs: scripts
+ $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $@
+dtbs_install: prepare scripts
$(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $@
# We use MRPROPER_FILES and CLEAN_FILES now
next prev parent reply other threads:[~2014-09-26 14:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 10:15 Grant Likely
2014-04-01 19:42 ` Paul Bolle
2014-04-01 20:18 ` Rob Herring
2014-04-01 20:34 ` Paul Bolle
2014-04-01 20:32 ` Grant Likely
2014-04-01 20:39 ` Grant Likely
2014-04-01 20:46 ` Paul Bolle
2014-09-26 12:30 ` Linus Walleij
2014-09-26 14:19 ` Jason Cooper [this message]
2014-09-29 8:52 ` Linus Walleij
2014-10-27 15:39 ` Linus Walleij
2014-11-02 20:52 ` [PATCH] ARM: kbuild: Fix forced rebuild after 'make dtbs' Jason Cooper
2014-11-25 21:41 ` Michal Marek
2014-11-25 23:51 ` Russell King - ARM Linux
2014-11-26 0:57 ` Jason Cooper
2014-11-26 13:57 ` Linus Walleij
2014-11-26 14:41 ` Russell King - ARM Linux
2014-11-28 14:10 ` Linus Walleij
2014-12-01 13:55 ` Michal Marek
2014-12-04 11:22 ` Grant Likely
2014-12-04 11:24 ` Russell King - ARM Linux
2014-11-26 9:39 ` Michal Marek
2014-09-29 12:49 ` [git pull] Devicetree changes for v3.15 Grant Likely
2014-09-29 13:52 ` Jason Cooper
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=20140926141943.GC23926@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@linaro.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®