From: Rob Herring <robh@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
john@phrozen.org, robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, neil@brown.name,
devel@driverdev.osuosl.org, tsbogend@alpha.franken.de,
linux-clk@vger.kernel.org, sboyd@kernel.org
Subject: Re: [PATCH v10 2/6] dt: bindings: add mt7621-sysc device tree binding documentation
Date: Mon, 8 Mar 2021 15:55:53 -0700 [thread overview]
Message-ID: <20210308225553.GA3102663@robh.at.kernel.org> (raw)
In-Reply-To: <20210307070426.15933-3-sergio.paracuellos@gmail.com>
On Sun, 07 Mar 2021 08:04:22 +0100, Sergio Paracuellos wrote:
> Adds device tree binding documentation for clocks in the
> MT7621 SOC.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> .../bindings/clock/mediatek,mt7621-sysc.yaml | 68 +++++++++++++++++++
> 1 file changed, 68 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt7621-sysc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-03-08 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 7:04 [PATCH v10 0/6] MIPS: ralink: add CPU clock detection and clock driver for MT7621 Sergio Paracuellos
2021-03-07 7:04 ` [PATCH v10 1/6] dt-bindings: clock: add dt binding header for mt7621 clocks Sergio Paracuellos
2021-03-07 7:04 ` [PATCH v10 2/6] dt: bindings: add mt7621-sysc device tree binding documentation Sergio Paracuellos
2021-03-08 22:55 ` Rob Herring [this message]
2021-03-07 7:04 ` [PATCH v10 3/6] clk: ralink: add clock driver for mt7621 SoC Sergio Paracuellos
2021-03-07 7:04 ` [PATCH v10 4/6] staging: mt7621-dts: make use of new 'mt7621-clk' Sergio Paracuellos
2021-03-07 7:04 ` [PATCH v10 5/6] staging: mt7621-dts: use valid vendor 'mediatek' instead of invalid 'mtk' Sergio Paracuellos
2021-03-07 7:04 ` [PATCH v10 6/6] MAINTAINERS: add MT7621 CLOCK maintainer Sergio Paracuellos
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=20210308225553.GA3102663@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john@phrozen.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=neil@brown.name \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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).