From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH] dt-bindings: clk: emev2: Convert to json-schema
Date: Thu, 6 May 2021 15:46:15 -0500 [thread overview]
Message-ID: <20210506204615.GA773568@robh.at.kernel.org> (raw)
In-Reply-To: <526e1a412145a0fcc5a43dcf6de5c580301017cb.1620119350.git.geert+renesas@glider.be>
On Tue, 04 May 2021 11:10:20 +0200, Geert Uytterhoeven wrote:
> Convert the Renesas EMMA Mobile EV2 System Management Unit (SMU) Device
> Tree binding documentation to json-schema.
>
> Drop the separate provider examples, as they mostly duplicate the global
> example. Drop the consumer example, as it doesn't belong here.
> Update the global example to match reality.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> This is a very old common clock binding, describing all clocks in detail
> in DT, grouped under a "clocks" node.
> ---
> .../bindings/clock/renesas,emev2-smu.txt | 98 ------------
> .../bindings/clock/renesas,emev2-smu.yaml | 140 ++++++++++++++++++
> 2 files changed, 140 insertions(+), 98 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/renesas,emev2-smu.txt
> create mode 100644 Documentation/devicetree/bindings/clock/renesas,emev2-smu.yaml
>
Applied, thanks!
prev parent reply other threads:[~2021-05-06 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 9:10 [PATCH] dt-bindings: clk: emev2: Convert to json-schema Geert Uytterhoeven
2021-05-06 20:46 ` Rob Herring [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=20210506204615.GA773568@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).