From: Andrew Davis <afd@ti.com>
To: Nicolas Schier <nicolas@fjasle.eu>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Michal Marek <michal.lkml@markovi.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Frank Rowand <frowand.list@gmail.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
<devicetree@vger.kernel.org>, <linux-kbuild@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: Disallow DTB overlays to built from .dts named source files
Date: Mon, 15 May 2023 11:48:51 -0500 [thread overview]
Message-ID: <1118291b-1137-6368-6202-e54151f01eb0@ti.com> (raw)
In-Reply-To: <b3820dd3-83dd-278e-e9ad-814be0bc8cfa@ti.com>
On 3/8/23 9:01 AM, Andrew Davis wrote:
> On 3/8/23 10:56 AM, Nicolas Schier wrote:
>> On Mon, Mar 06, 2023 at 04:47:52PM -0600 Andrew Davis wrote:
>>> As a follow up to the series allowing DTB overlays to built from .dtso
>>> files. Now that all overlays have been renamed, remove the ability to
>>> build from overlays from .dts files to prevent any files with the old
>> ^^^^
>>
>> The first "from" sounds superfluous to me.
>>
>
> It is a typo, feel free to drop it locally whoever takes this patch.
>
Seems no one took this last cycle.. Still valid and applies for this one.
Andrew
> Thanks,
> Andrew
>
>> Kind regards,
>> Nicolas
>>> name from accidental being added.
>>>
>>> Signed-off-by: Andrew Davis <afd@ti.com>
>>> ---
>>> scripts/Makefile.lib | 3 ---
>>> 1 file changed, 3 deletions(-)
>>>
>>> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
>>> index 100a386fcd71..68d0134bdbf9 100644
>>> --- a/scripts/Makefile.lib
>>> +++ b/scripts/Makefile.lib
>>> @@ -418,9 +418,6 @@ endif
>>> $(obj)/%.dtb: $(src)/%.dts $(DTC) $(DT_TMP_SCHEMA) FORCE
>>> $(call if_changed_dep,dtb)
>>> -$(obj)/%.dtbo: $(src)/%.dts $(DTC) FORCE
>>> - $(call if_changed_dep,dtc)
>>> -
>>> $(obj)/%.dtbo: $(src)/%.dtso $(DTC) FORCE
>>> $(call if_changed_dep,dtc)
>>> --
>>> 2.39.2
>>
next prev parent reply other threads:[~2023-05-15 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 22:47 [PATCH] kbuild: Disallow DTB overlays to built from .dts named source files Andrew Davis
2023-03-07 2:36 ` Masahiro Yamada
2023-03-07 7:59 ` Geert Uytterhoeven
2023-03-07 11:55 ` Andy Shevchenko
2023-03-08 16:56 ` Nicolas Schier
2023-03-08 17:01 ` Andrew Davis
2023-05-15 16:48 ` Andrew Davis [this message]
2023-05-22 1:36 ` Masahiro Yamada
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=1118291b-1137-6368-6202-e54151f01eb0@ti.com \
--to=afd@ti.com \
--cc=andriy.shevchenko@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=vigneshr@ti.com \
/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