From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Vincent Guittot <vincent.guittot@linaro.org>,
David Gibson <david@gibson.dropbear.id.au>,
Michal Simek <michal.simek@xilinx.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
anmar.oueja@linaro.org, Bill Mills <bill.mills@linaro.org>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] of: unittest: rename overlay source files from .dts to .dtso
Date: Sat, 27 Mar 2021 11:40:35 -0600 [thread overview]
Message-ID: <20210327174035.GA291160@robh.at.kernel.org> (raw)
In-Reply-To: <20210324223713.1334666-1-frowand.list@gmail.com>
On Wed, Mar 24, 2021 at 05:37:13PM -0500, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Add Makefile rule to build .dtbo.o assembly file from overlay .dtso
> source file.
>
> Rename unittest .dts overlay source files to use .dtso suffix.
I'm pretty lukewarm on .dtso...
>
> Update Makefile to build .dtbo.o objects instead of .dtb.o from
> unittest overlay source files.
>
> Modify unitest.c to use .dtbo.o based symbols instead of .dtb.o
>
> Modify Makefile.lib %.dtbo rule to depend upon %.dtso instead of %.dts
>
> Documentation/devicetree/of_unittest.rst was already out of date.
> This commit would make it even more out of date. Delete the document
> instead of continuing the maintenance burden of keeping the document
> in sync with the source.
This should be a separate change. It's also going to collide with my doc
improvements.
Improvements here would be better than just deleting.
next prev parent reply other threads:[~2021-03-27 17:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 22:37 [PATCH 1/1] of: unittest: rename overlay source files from .dts to .dtso frowand.list
2021-03-25 4:41 ` [PATCH V4] kbuild: Add rule to build .dt.yaml files for overlays Viresh Kumar
2021-03-27 17:40 ` Rob Herring [this message]
2021-03-29 19:23 ` [PATCH 1/1] of: unittest: rename overlay source files from .dts to .dtso Frank Rowand
2021-04-22 8:44 ` Geert Uytterhoeven
2021-04-22 18:54 ` Frank Rowand
2021-05-26 6:11 ` Viresh Kumar
2021-05-26 21:21 ` Frank Rowand
2021-05-27 1:22 ` David Gibson
2021-05-27 7:21 ` Geert Uytterhoeven
2021-05-28 3:45 ` David Gibson
2021-05-29 10:16 ` Geert Uytterhoeven
2021-06-22 9:44 ` Geert Uytterhoeven
2021-08-24 9:20 ` Geert Uytterhoeven
2022-01-06 9:00 ` Geert Uytterhoeven
2022-01-06 17:23 ` Frank Rowand
2022-01-14 2:10 ` Rob Herring
2022-01-14 9:25 ` Geert Uytterhoeven
2022-01-18 9:54 ` David Gibson
2022-01-26 19:31 ` Rob Herring
2022-04-27 21:14 ` Rob Herring
2022-04-28 6:25 ` Geert Uytterhoeven
2022-04-28 13:05 ` Rob Herring
2022-04-28 18:16 ` Frank Rowand
2021-05-27 16:23 ` Frank Rowand
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=20210327174035.GA291160@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=anmar.oueja@linaro.org \
--cc=bill.mills@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=michal.simek@xilinx.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).