From: Rob Herring <robh@kernel.org>
To: conor.dooley@microchip.com
Cc: sboyd@kernel.org, linux-clk@vger.kernel.org, palmer@dabbelt.com,
mturquette@baylibre.com, geert@linux-m68k.org,
cyril.jean@microchip.com, david.abdurachmanov@gmail.com,
krzysztof.kozlowski@canonical.com, devicetree@vger.kernel.org,
daire.mcnamara@microchip.com, robh+dt@kernel.org
Subject: Re: [PATCH v7 1/2] dt-bindings: clk: microchip: Add Microchip PolarFire host binding
Date: Wed, 15 Dec 2021 09:51:30 -0600 [thread overview]
Message-ID: <YboPAmeRMNKCUpCf@robh.at.kernel.org> (raw)
In-Reply-To: <20211215083002.1353-2-conor.dooley@microchip.com>
On Wed, 15 Dec 2021 08:30:01 +0000, conor.dooley@microchip.com wrote:
> From: Daire McNamara <daire.mcnamara@microchip.com>
>
> Add device tree bindings for the Microchip PolarFire system
> clock controller
>
> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../bindings/clock/microchip,mpfs.yaml | 61 +++++++++++++++++++
> .../dt-bindings/clock/microchip,mpfs-clock.h | 45 ++++++++++++++
> 2 files changed, 106 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/microchip,mpfs.yaml
> create mode 100644 include/dt-bindings/clock/microchip,mpfs-clock.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-15 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 8:30 [PATCH v7 0/2] CLK: microchip: Add clkcfg driver for Microchip PolarFire SoC conor.dooley
2021-12-15 8:30 ` [PATCH v7 1/2] dt-bindings: clk: microchip: Add Microchip PolarFire host binding conor.dooley
2021-12-15 15:51 ` Rob Herring [this message]
2021-12-15 18:09 ` Geert Uytterhoeven
2021-12-15 8:30 ` [PATCH v7 2/2] clk: microchip: Add driver for Microchip PolarFire SoC conor.dooley
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=YboPAmeRMNKCUpCf@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=david.abdurachmanov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.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).