From: Rob Herring <robh@kernel.org>
To: Zelong Dong <zelong.dong@amlogic.com>
Cc: jbrunet@baylibre.com, linux-arm-kernel@lists.infradead.org,
narmstrong@baylibre.com, robh+dt@kernel.org,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, p.zabel@pengutronix.de,
khilman@baylibre.com, martin.blumenstingl@googlemail.com
Subject: Re: [PATCH 2/3] dt-bindings: reset: add bindings for the Meson-S4 SoC Reset Controller
Date: Mon, 10 Jan 2022 11:36:02 -0600 [thread overview]
Message-ID: <YdxugtL5PsrwsT6D@robh.at.kernel.org> (raw)
In-Reply-To: <20220107023931.13251-3-zelong.dong@amlogic.com>
On Fri, 07 Jan 2022 10:39:30 +0800, Zelong Dong wrote:
> Add DT bindings for the Meson-S4 SoC Reset Controller include file.
>
> Signed-off-by: Zelong Dong <zelong.dong@amlogic.com>
> ---
> .../reset/amlogic,meson-s4-reset.h | 125 ++++++++++++++++++
> 1 file changed, 125 insertions(+)
> create mode 100644 include/dt-bindings/reset/amlogic,meson-s4-reset.h
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
next prev parent reply other threads:[~2022-01-10 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:39 [PATCH 0/3] reset: meson-s4: add reset driver Zelong Dong
2022-01-07 2:39 ` [PATCH 1/3] dt-bindings: reset: Add compatible for Meson-S4 Reset Controller Zelong Dong
2022-01-07 21:56 ` Martin Blumenstingl
2022-01-12 1:48 ` Rob Herring
2022-01-07 2:39 ` [PATCH 2/3] dt-bindings: reset: add bindings for the Meson-S4 SoC " Zelong Dong
2022-01-07 21:57 ` Martin Blumenstingl
2022-01-10 17:36 ` Rob Herring [this message]
2022-01-07 2:39 ` [PATCH 3/3] reset: reset-meson: add support " Zelong Dong
2022-01-07 21:58 ` Martin Blumenstingl
2022-04-04 10:17 ` [PATCH 0/3] reset: meson-s4: add reset driver Philipp Zabel
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=YdxugtL5PsrwsT6D@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=zelong.dong@amlogic.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).