devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Michal Simek <michal.simek@xilinx.com>,
	Anmar Oueja <anmar.oueja@linaro.org>,
	Bill Mills <bill.mills@linaro.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Subject: Re: [PATCH 1/1] of: unittest: rename overlay source files from .dts to .dtso
Date: Thu, 28 Apr 2022 08:05:47 -0500	[thread overview]
Message-ID: <YmqRK1uWiady7BHD@robh.at.kernel.org> (raw)
In-Reply-To: <CAMuHMdUyuJbyHthc4ATuRXY=zM_Vbc7DmsZvWgX_u8w3FfhzDg@mail.gmail.com>

On Thu, Apr 28, 2022 at 08:25:31AM +0200, Geert Uytterhoeven wrote:
> Hi Rob,
> 
> On Wed, Apr 27, 2022 at 11:14 PM Rob Herring <robh@kernel.org> wrote:
> > On Wed, Jan 26, 2022 at 1:31 PM Rob Herring <robh@kernel.org> wrote:
> > > On Fri, Jan 14, 2022 at 3:25 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > > On Fri, Jan 14, 2022 at 3:10 AM Rob Herring <robh@kernel.org> wrote:
> > > > > On Thu, Jan 6, 2022 at 11:23 AM Frank Rowand <frowand.list@gmail.com> wrote:
> > > > > > Patient Geert has pinged again.
> > > > >
> > > > > If it's not a patch to be reviewed, then I'm not going to see it most
> > > > > likely. I don't read the DT list regularly...
> > > >
> > > > Fair enough...
> > > >
> > > > > > If I remember correctly you guys were not thrilled with this idea, but
> > > > > > also did not seem strongly against it.  Are you willing to go along
> > > > > > with .dtso for overlay source files?  If so, I will revive this patch
> > > > > > series.
> > > > > >
> > > > > > David, if you are against supporting .dtso in the dtc compiler then
> > > > > > the kernel can still support it through make rules.
> > > > >
> > > > > I'm not really interested in diverging from dtc. I'd suggest moving
> > > > > the discussion to dtc list and/or devicetree-spec if you want to get
> > > > > more attention on this.
> > > >
> > > > What needs to be supported in the dtc compiler?
> > > > The fallback passed to guess_input_format() is "dts".
> > > > So this has been working out-of-the-box since forever?
> > >
> > > Ah, okay.
> > >
> > > > > Also, keep in mind that extensions also affect MIME types which
> > > > > someone was also asking about recently.
> > > >
> > > > You mean "MIME type of Devicetree Blobs and Sources"[1]?
> > > > According to [2](2022-01-13), none of that has happened.
> > >
> > > This is what I was thinking of:
> > >
> > > https://github.com/devicetree-org/devicetree-specification/issues/46
> > >
> > > In any case, given everyone is ambivalent, send me an updated patch
> > > and I'll apply it.

^^^^^^^^

> >
> > Ping! Anyone still want this?
> >
> > What I don't want to see is a mixture of .dts and .dtso. And now I'm
> > reviewing RPi overlay patches[1] with .dts.
> 
> I still prefer .dtso over .dts, as it allows tools to detect the file
> type without having to read the file's contents.
> Without this, e.g. make needs to have all overlays listed explicitly
> in a Makefile.
> 
> We do have .c, .h, .s (even .S), .dtsi. So why not .dtso?

Read above! I said to resend this patch and I will apply it.

Rob

  reply	other threads:[~2022-04-28 13:05 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 ` [PATCH 1/1] of: unittest: rename overlay source files from .dts to .dtso Rob Herring
2021-03-29 19:23   ` 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 [this message]
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=YmqRK1uWiady7BHD@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@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=pantelis.antoniou@konsulko.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).