From: Rob Herring <robh@kernel.org>
To: Romain Perier <romain.perier@gmail.com>
Cc: linux-watchdog@vger.kernel.org, Daniel Palmer <daniel@0x0f.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Mohammed Billoo <mohammed.billoo@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: watchdog: Add Mstar MSC313e WDT devicetree bindings documentation
Date: Thu, 10 Jun 2021 11:57:02 -0500 [thread overview]
Message-ID: <20210610165702.GA1960781@robh.at.kernel.org> (raw)
In-Reply-To: <20210605170441.33667-2-romain.perier@gmail.com>
On Sat, 05 Jun 2021 19:04:39 +0200, Romain Perier wrote:
> This adds the documentation for the devicetree bindings of the Mstar
> MSC313e watchdog driver, found from MSC313e SoCs and newer.
>
> Signed-off-by: Romain Perier <romain.perier@gmail.com>
> ---
> .../bindings/watchdog/mstar,msc313e-wdt.yaml | 40 +++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/mstar,msc313e-wdt.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-06-10 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 17:04 [PATCH v3 0/3] Add watchdog for Mstar SoCs Romain Perier
2021-06-05 17:04 ` [PATCH v3 1/3] dt-bindings: watchdog: Add Mstar MSC313e WDT devicetree bindings documentation Romain Perier
2021-06-10 16:57 ` Rob Herring [this message]
2021-06-05 17:04 ` [PATCH v3 2/3] watchdog: Add Mstar MSC313e WDT driver Romain Perier
2021-06-05 20:26 ` Guenter Roeck
2021-06-11 10:34 ` Guenter Roeck
2021-06-11 14:35 ` Romain Perier
2021-06-11 15:13 ` Guenter Roeck
2021-06-05 17:04 ` [PATCH v3 3/3] ARM: dts: mstar: Add watchdog device_node definition Romain Perier
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=20210610165702.GA1960781@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mohammed.billoo@gmail.com \
--cc=robh+dt@kernel.org \
--cc=romain.perier@gmail.com \
--cc=wim@linux-watchdog.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).