All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v2] dt-bindings: clock: renesas: cpg-mssr: Convert to json-schema
Date: Tue, 10 Mar 2020 15:55:04 -0500	[thread overview]
Message-ID: <20200310205504.GA27288@bogus> (raw)
In-Reply-To: <20200303094848.23670-1-geert+renesas@glider.be>

On Tue,  3 Mar 2020 10:48:48 +0100, Geert Uytterhoeven wrote:
> Convert the Renesas Clock Pulse Generator / Module Standby and Software
> Reset Device Tree binding documentation to json-schema.
> 
> Note that #reset-cells was incorrecty marked a required property for
> RZ/A2 before.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> To be queued in clk-renesas-for-v5.7.
> 
> v2:
>   - Remove complex if-construct implementing per-SoC clocks/clock-names
>     constraints; list all possible clock-names upfront instead,
>   - Drop Clock Domain member example.
> ---
>  .../bindings/clock/renesas,cpg-mssr.txt       | 100 ---------------
>  .../bindings/clock/renesas,cpg-mssr.yaml      | 119 ++++++++++++++++++
>  2 files changed, 119 insertions(+), 100 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-mssr.txt
>  create mode 100644 Documentation/devicetree/bindings/clock/renesas,cpg-mssr.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2020-03-10 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  9:48 [PATCH v2] dt-bindings: clock: renesas: cpg-mssr: Convert to json-schema Geert Uytterhoeven
2020-03-05 21:54 ` Stephen Boyd
2020-03-10 20:55 ` Rob Herring [this message]
2020-03-11  8:08   ` Geert Uytterhoeven
2020-03-12  8:30     ` Geert Uytterhoeven

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=20200310205504.GA27288@bogus \
    --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=mturquette@baylibre.com \
    --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 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.