Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752165AbaJ0PjL (ORCPT ); Mon, 27 Oct 2014 11:39:11 -0400 Received: from mail-ig0-f171.google.com ([209.85.213.171]:61557 "EHLO mail-ig0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751565AbaJ0PjJ (ORCPT ); Mon, 27 Oct 2014 11:39:09 -0400 MIME-Version: 1.0 In-Reply-To: References: <20140926141943.GC23926@titan.lakedaemon.net> Date: Mon, 27 Oct 2014 16:39:08 +0100 Message-ID: Subject: Re: [git pull] Devicetree changes for v3.15 From: Linus Walleij To: Jason Cooper Cc: Grant Likely , Linus Torvalds , "devicetree@vger.kernel.org" , Linux Kernel Mailing List , Rob Herring Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 29, 2014 at 10:52 AM, Linus Walleij wrote: > On Fri, Sep 26, 2014 at 4:19 PM, Jason Cooper wrote: >> On Fri, Sep 26, 2014 at 02:30:53PM +0200, Linus Walleij wrote: > >> 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? > > Yes! > Tested-by: Linus Walleij > > Please get this upstream marked for stable. So is there a proper fix for this coming or not? I am suffering from this problem :-( Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/