From: Andreas Kemnade <andreas@kemnade.info>
To: Andrew Davis <afd@ti.com>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<tony@atomide.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: omap: Convert omap.txt to yaml
Date: Tue, 4 Apr 2023 23:40:54 +0200 [thread overview]
Message-ID: <20230404234054.30d806af@aktux> (raw)
In-Reply-To: <4b9ad103-3210-18cc-50f9-935d95a1efa3@ti.com>
On Tue, 4 Apr 2023 16:09:31 -0500
Andrew Davis <afd@ti.com> wrote:
> On 4/4/23 3:58 PM, Andreas Kemnade wrote:
> > From: Andrew Davis <afd@ti.com>
> >
> > Convert omap.txt to yaml.
> >
> > CC: linux-omap@vger.kernel.org
> > Signed-off-by: Andrew Davis <afd@ti.com>
> > [various cleanup, adding Epson Moverio BT-200]
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > ---
> > .../devicetree/bindings/arm/omap/omap.txt | 152 ------------------
> > Documentation/devicetree/bindings/arm/ti.yaml | 147 +++++++++++++++++
>
> How about
>
> Documentation/devicetree/bindings/arm/ti/omap.yaml
>
> as we already have a arm/ti/k3.yaml for our K3 devices.
>
makes sense.
I was just following this:
> > Move this to arm/ti,omap.yaml or arm/ti.yaml. The rest of omap/ dir
> > should get moved elsewhere eventually.
>
> ACK
from Rob and you.
But your current idea seems better.
Regards,
Andreas
next prev parent reply other threads:[~2023-04-04 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 20:58 [PATCH v4 0/2] dt-bindings: omap: Convert omap.txt to yaml Andreas Kemnade
2023-04-04 20:58 ` [PATCH v4 1/2] " Andreas Kemnade
2023-04-04 21:09 ` Andrew Davis
2023-04-04 21:40 ` Andreas Kemnade [this message]
2023-04-04 20:58 ` [PATCH v4 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=20230404234054.30d806af@aktux \
--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.