devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Andrew Davis <afd@ti.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Colin Foster" <colin.foster@in-advantage.com>,
	"Olof Johansson" <olof@lixom.net>,
	"Arnd Bergmann" <arnd@arndb.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 0/2] Convert omap.txt to DT schema
Date: Fri, 17 Feb 2023 07:48:25 +0200	[thread overview]
Message-ID: <Y+8VKZHAWwNr1ED4@atomide.com> (raw)
In-Reply-To: <20230216153339.19987-1-afd@ti.com>

* Andrew Davis <afd@ti.com> [230216 15:33]:
> I saw there was some more talk on the lists about converting
> the omap.txt over to DT schema. I remembered that I had made
> an attempt at this and wanted to post it as a WIP example.
> It is not perfect or even very good, but might serve as
> a base for someone.

Hey that's great :)

Tony

      parent reply	other threads:[~2023-02-17  5:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 15:33 [RFC 0/2] Convert omap.txt to DT schema Andrew Davis
2023-02-16 15:33 ` [RFC 1/2] ARM: dts: omap: Drop ti,omap36xx compatible Andrew Davis
2023-03-27 19:18   ` Andreas Kemnade
2023-03-28  5:01     ` Tony Lindgren
2023-03-28  7:06       ` Andreas Kemnade
2023-03-28  7:08         ` Tony Lindgren
2023-03-28  7:27           ` Tony Lindgren
2023-02-16 15:33 ` [RFC 2/2] WIP: dt-bindings: omap: Convert omap.txt to yaml Andrew Davis
2023-02-16 16:08   ` H. Nikolaus Schaller
2023-02-16 16:19     ` Andrew Davis
2023-02-16 16:43       ` H. Nikolaus Schaller
2023-02-16 16:41   ` Rob Herring
2023-02-16 17:30     ` Andrew Davis
2023-02-17  5:48 ` Tony Lindgren [this message]

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=Y+8VKZHAWwNr1ED4@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=bcousson@baylibre.com \
    --cc=colin.foster@in-advantage.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.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).