From: Matthias Brugger <matthias.bgg@gmail.com>
To: Yassine Oudjana <yassine.oudjana@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Sam Shih <sam.shih@mediatek.com>, Stephen Boyd <sboyd@kernel.org>,
Ryder Lee <ryder.lee@kernel.org>,
Yassine Oudjana <y.oudjana@protonmail.com>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] dt-bindings: arm: mediatek: Convert some docs to DT schema
Date: Wed, 20 Apr 2022 14:30:17 +0200 [thread overview]
Message-ID: <3c24dbdb-7677-bba6-685a-43293a01e777@gmail.com> (raw)
In-Reply-To: <20220419180938.19397-1-y.oudjana@protonmail.com>
On 19/04/2022 20:09, Yassine Oudjana wrote:
> From: Yassine Oudjana <y.oudjana@protonmail.com>
>
> This series includes DT schema conversions for topckgen, apmixedsys
> and infracfg bindings.
>
Thanks for the effort. Regarding the bindings Krzysztof mentioned should go into
bindings/clock/ directory: please add the clock maintainers as maintainers of
the bindings.
Thanks!
Matthias
> Yassine Oudjana (3):
> dt-bindings: arm: mediatek: topckgen: Convert to DT schema
> dt-bindings: arm: mediatek: apmixedsys: Convert to DT schema
> dt-bindings: arm: mediatek: infracfg: Convert to DT schema
>
> .../arm/mediatek/mediatek,apmixedsys.txt | 35 --------
> .../arm/mediatek/mediatek,apmixedsys.yaml | 60 ++++++++++++++
> .../arm/mediatek/mediatek,infracfg.txt | 42 ----------
> .../arm/mediatek/mediatek,infracfg.yaml | 79 +++++++++++++++++++
> .../arm/mediatek/mediatek,topckgen.txt | 35 --------
> .../arm/mediatek/mediatek,topckgen.yaml | 60 ++++++++++++++
> 6 files changed, 199 insertions(+), 112 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,apmixedsys.txt
> create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,apmixedsys.yaml
> delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,infracfg.txt
> create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,infracfg.yaml
> delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,topckgen.txt
> create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,topckgen.yaml
>
prev parent reply other threads:[~2022-04-20 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 18:09 [PATCH 0/3] dt-bindings: arm: mediatek: Convert some docs to DT schema Yassine Oudjana
2022-04-19 18:09 ` [PATCH 1/3] dt-bindings: arm: mediatek: topckgen: Convert " Yassine Oudjana
2022-04-20 6:47 ` Krzysztof Kozlowski
2022-04-20 6:48 ` Krzysztof Kozlowski
2022-04-19 18:09 ` [PATCH 2/3] dt-bindings: arm: mediatek: apmixedsys: " Yassine Oudjana
2022-04-20 6:50 ` Krzysztof Kozlowski
2022-04-19 18:09 ` [PATCH 3/3] dt-bindings: arm: mediatek: infracfg: " Yassine Oudjana
2022-04-20 1:19 ` Rob Herring
2022-04-20 6:54 ` Krzysztof Kozlowski
2022-04-20 12:30 ` Matthias Brugger [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=3c24dbdb-7677-bba6-685a-43293a01e777@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=sam.shih@mediatek.com \
--cc=sboyd@kernel.org \
--cc=y.oudjana@protonmail.com \
--cc=yassine.oudjana@gmail.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 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).