linux-kernel - Re: [git pull] Devicetree changes for v3.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdZoo=P7uTO1rNDD_HUPjfAk26C0=mNYPoZmTV0wcO3V-w@mail.gmail.com>
Date:	Fri, 26 Sep 2014 14:30:53 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Grant Likely <grant.likely@...retlab.ca>,
	Jason Cooper <jason@...edaemon.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Rob Herring <rob.herring@...aro.org>
Subject: Re: [git pull] Devicetree changes for v3.15

On Tue, Apr 1, 2014 at 12:15 PM, Grant Likely <grant.likely@...retlab.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

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...

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/