From: Andreas Kemnade <andreas@kemnade.info>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
tony@atomide.com, andreas@kemnade.info, afd@ti.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: [PATCH v6 0/2] dt-bindings: omap: Convert omap.txt to yaml
Date: Wed, 5 Apr 2023 18:19:06 +0200 [thread overview]
Message-ID: <20230405161908.4312-1-andreas@kemnade.info> (raw)
Convert board compatibles to yaml and add the new yaml file to
MAINTAINERS so that emails are properly distributed
Changes in V6:
- reflect the rename also in the file header
Changes in V5:
- renamed the new file to ti/omap.yaml
Changes in V4:
- fix order
- re-add dra7 to .txt to have it sorted out later
Changes in V3:
- update MAINTAINERS
- remove converted stuff from .txt
Changes in V2:
- renamed file
- fixed gta04
- added Openpandora, Epson Moverio BT-200
- drop example
- remove descriptions if just reformatting the name
Andreas Kemnade (1):
MAINTAINERS: add board bindings list to OMAP2+ files
Andrew Davis (1):
dt-bindings: omap: Convert omap.txt to yaml
.../devicetree/bindings/arm/omap/omap.txt | 152 ------------------
.../devicetree/bindings/arm/ti/omap.yaml | 147 +++++++++++++++++
MAINTAINERS | 1 +
3 files changed, 148 insertions(+), 152 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/ti/omap.yaml
--
2.39.2
next reply other threads:[~2023-04-05 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 16:19 Andreas Kemnade [this message]
2023-04-05 16:19 ` [PATCH v6 1/2] dt-bindings: omap: Convert omap.txt to yaml Andreas Kemnade
2023-04-06 8:32 ` Krzysztof Kozlowski
2023-04-06 8:36 ` Krzysztof Kozlowski
2023-04-06 18:35 ` Andreas Kemnade
2023-04-06 18:46 ` Krzysztof Kozlowski
2023-05-11 21:28 ` Andreas Kemnade
2023-04-05 16:19 ` [PATCH v6 2/2] MAINTAINERS: add board bindings list to OMAP2+ files Andreas Kemnade
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=20230405161908.4312-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.