From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B5E61C43219 for ; Sun, 13 Nov 2022 12:36:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233954AbiKMMgm (ORCPT ); Sun, 13 Nov 2022 07:36:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232884AbiKMMgl (ORCPT ); Sun, 13 Nov 2022 07:36:41 -0500 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C0DCCFCE3; Sun, 13 Nov 2022 04:36:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668343000; x=1699879000; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=tXxNoJ4p40NbDu6Pg1fz6lrpeT1kuob3UG5D0fgt2iE=; b=mUe+O9R/P5NPzbu60fYjQhCx5ATrF+vmakHBufEnZSkoANTQEKwoDGgw 5YEYlXk4BvVX9indhORoKE78alibfyFLvQOBa3js5JrJfvowB0lIq8h1H EANWgBCv5d1TwE5qRgf+F2ZeWc2WToUdEy21EeC2rUV8julZECl9anYk6 BoOupdOSO4NoMGwmb75hXyacCB8h/tg5INXvF55kDtgUy1BK8ZKoPHS/h cjJ57qsXUtKca6svZumXhoXxE4pHAczNOOWyQJfKXwcHvggfN+ehtYPSg c1hNw3J3gsWDcuEwf/dXiUbEWGTqSFcK8bsnedLWw0cPUypdMv0uyMJ7B A==; X-IronPort-AV: E=McAfee;i="6500,9779,10529"; a="338588356" X-IronPort-AV: E=Sophos;i="5.96,161,1665471600"; d="scan'208";a="338588356" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Nov 2022 04:36:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10529"; a="615963179" X-IronPort-AV: E=Sophos;i="5.96,161,1665471600"; d="scan'208";a="615963179" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga006.jf.intel.com with ESMTP; 13 Nov 2022 04:36:35 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ouCDx-00Bfz5-0E; Sun, 13 Nov 2022 14:36:33 +0200 Date: Sun, 13 Nov 2022 14:36:32 +0200 From: Andy Shevchenko To: Andrew Davis Cc: Rob Herring , Shawn Guo , Li Yang , Sascha Hauer , Krzysztof Kozlowski , Nishanth Menon , Vignesh Raghavendra , Masahiro Yamada , Michal Marek , Nick Desaulniers , Geert Uytterhoeven , Frank Rowand , devicetree@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/7] Rename DTB overlay source files Message-ID: References: <20221024173434.32518-1-afd@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Sun, Nov 13, 2022 at 02:20:48PM +0200, Andy Shevchenko wrote: > On Fri, Nov 11, 2022 at 03:05:20PM -0600, Andrew Davis wrote: > > On 11/11/22 1:39 PM, Andy Shevchenko wrote: > > > On Wed, Oct 26, 2022 at 09:11:21AM -0500, Rob Herring wrote: > > > > On Mon, Oct 24, 2022 at 12:34 PM Andrew Davis wrote: > > > > > > > > > > Hello all, > > > > > > > > > > This is a series based on my patch here[0]. As suggested by Rob > > > > > I've resurrected Frank's patch and appended it to mine as a series. > > > > > > > > > > First patch here is my original patch, 3rd is Frank's patch but with > > > > > the unittest changes pulled out into the 2nd patch. That was re-worked > > > > > moving the source building macro into scripts/Makefile.lib. > > > > > > > > > > Patches 4, 5, and 6 are an attempt at renaming all the existing DTB > > > > > overlays. Split out by platform so they could be taken by platform > > > > > maintainers or if easier ACK'd here and taken all together. > > > > > > > > > > This should cover all the DTB overlays so we can remove the old .dts > > > > > rule for overlays and make .dtso the only supported way, let me know > > > > > if we want that this cycle and I can post that too. > > > > > > > > > > Thanks, > > > > > Andrew > > > > > > > > > > Changes from v1[1]: > > > > > - Added patch to rename pi433 overlay. > > > > > - Cleaned wording on patch 4-6. > > > > > - Collected some ACKs > > > > > > > > > > [0] https://www.spinics.net/lists/kernel/msg4548509.html > > > > > [1] https://www.spinics.net/lists/arm-kernel/msg1020165.html > > > > > > > > > > Andrew Davis (6): > > > > > kbuild: Allow DTB overlays to built from .dtso named source files > > > > > kbuild: Allow DTB overlays to built into .dtso.S files > > > > > arm64: dts: freescale: Rename DTB overlay source files from .dts to > > > > > .dtso > > > > > arm64: dts: renesas: Rename DTB overlay source files from .dts to > > > > > .dtso > > > > > arm64: dts: xilinx: Rename DTB overlay source files from .dts to .dtso > > > > > staging: pi433: overlay: Rename overlay source file from .dts to .dtso > > > > > > > > > > Frank Rowand (1): > > > > > of: overlay: rename overlay source files from .dts to .dtso > > > > > > > > I've applied patches 1-3 and 7. I'll send a PR for the branch to the > > > > platform maintainers after a few days in linux-next. > > > > > > The patch > > > > > > commit 941214a512d8c80d47e720c17ec17e8539175e93 > > > Author: Andrew Davis > > > Date: Mon Oct 24 12:34:29 2022 -0500 > > > > > > kbuild: Allow DTB overlays to built into .dtbo.S files > > > > > > broke the build reproducibility / no-op builds. > > > > > > Before: > > > 2+ execution of `make` on non-changed tree did nothing > > > > > > Now: > > > Each run of `make` (even without a single bit changed) restarts vmlinux > > > rebuild. > > > > > > Please, revert or fix. > > > > > > > I do not see this behavior. What config are you using? > > > > Not sure how this patch could be the root cause, it only adds > > a build target/rule, but doesn't actually use it anywhere yet.. > > For your reference I started with this one [1]. > > When I bisected, I just answered with defaults on whatever `make` told me at > the configuration stage. > > The actual `make` command I used: > > make O=/path/to/the/result W=1 C=1 CF=-D__CHECK_ENDIAN__ -j64 > > But there is nothing that can affect the described issue. Actually, O= might affect which Makefile is used and how. The C=, CF= are sparse flags, W= is just warning level. > [1]: https://p.defau.lt/?ZSOdGnNxF9v9AQtrfDo_KQ -- With Best Regards, Andy Shevchenko