From: Rob Herring <robh@kernel.org>
To: Sagar Kadam <sagar.kadam@sifive.com>
Cc: aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
tglx@linutronix.de, linux-pwm@vger.kernel.org,
palmer@dabbelt.com, jason@lakedaemon.net, yash.shah@sifive.com,
thierry.reding@gmail.com, lee.jones@linaro.org,
u.kleine-koenig@pengutronix.de, robh+dt@kernel.org,
paul.walmsley@sifive.com, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, maz@kernel.org,
mturquette@baylibre.com, devicetree@vger.kernel.org,
sboyd@kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: fu540: prci: convert PRCI bindings to json-schema
Date: Tue, 6 Oct 2020 13:42:44 -0500 [thread overview]
Message-ID: <20201006184244.GA2610231@bogus> (raw)
In-Reply-To: <1601393531-2402-2-git-send-email-sagar.kadam@sifive.com>
On Tue, 29 Sep 2020 21:02:09 +0530, Sagar Kadam wrote:
> FU540-C000 SoC from SiFive has a PRCI block, here we convert
> the device tree bindings from txt to YAML.
>
> Signed-off-by: Sagar Kadam <sagar.kadam@sifive.com>
> ---
> .../bindings/clock/sifive/fu540-prci.txt | 46 -----------------
> .../bindings/clock/sifive/fu540-prci.yaml | 60 ++++++++++++++++++++++
> 2 files changed, 60 insertions(+), 46 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/sifive/fu540-prci.txt
> create mode 100644 Documentation/devicetree/bindings/clock/sifive/fu540-prci.yaml
>
Applied, thanks!
next prev parent reply other threads:[~2020-10-06 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 15:32 [PATCH v2 0/3] convert sifive's prci, plic and pwm bindings to yaml Sagar Kadam
2020-09-29 15:32 ` [PATCH v2 1/3] dt-bindings: fu540: prci: convert PRCI bindings to json-schema Sagar Kadam
2020-10-06 18:42 ` Rob Herring [this message]
2020-10-07 3:38 ` Sagar Kadam
2020-09-29 15:32 ` [PATCH v2 2/3] dt-bindings: riscv: convert plic " Sagar Kadam
2020-10-06 18:44 ` Rob Herring
2020-09-29 15:32 ` [PATCH v2 3/3] dt-bindings: riscv: convert pwm " Sagar Kadam
2020-10-06 18:45 ` Rob Herring
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=20201006184244.GA2610231@bogus \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sagar.kadam@sifive.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yash.shah@sifive.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).