From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: xianwei.zhao@amlogic.com
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] arm64: dts: amlogic: Add S6 Reset Controller
Date: Thu, 25 Dec 2025 00:13:59 +0100 [thread overview]
Message-ID: <CAFBinCAYWy_VFY8a=AAGpv1+7f5AkWnHk3KDH3fqRMTZfjuNsg@mail.gmail.com> (raw)
In-Reply-To: <20251223-reset-s6-s7-s7d-v2-2-958f341449f1@amlogic.com>
On Tue, Dec 23, 2025 at 6:37 AM Xianwei Zhao via B4 Relay
<devnull+xianwei.zhao.amlogic.com@kernel.org> wrote:
[...]
> +#define RESET_MIP_DSI_HOST 93
should this be RESET_MIPI_DSI_HOST?
With either the typo fixed, or an explanation why MIP_DSI_HOST is correct:
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-12-24 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 5:37 [PATCH v2 0/4] Add support for Amlogic S6/S7/S7D Reset Xianwei Zhao via B4 Relay
2025-12-23 5:37 ` [PATCH v2 1/4] dt-bindings: reset: Add compatible for Amlogic S6/S7/S7D Xianwei Zhao via B4 Relay
2025-12-24 23:13 ` Martin Blumenstingl
2025-12-23 5:37 ` [PATCH v2 2/4] arm64: dts: amlogic: Add S6 Reset Controller Xianwei Zhao via B4 Relay
2025-12-24 23:13 ` Martin Blumenstingl [this message]
2025-12-23 5:37 ` [PATCH v2 3/4] arm64: dts: amlogic: Add S7 " Xianwei Zhao via B4 Relay
2025-12-24 23:15 ` Martin Blumenstingl
2025-12-23 5:37 ` [PATCH v2 4/4] arm64: dts: amlogic: Add S7D " Xianwei Zhao via B4 Relay
2025-12-24 23:34 ` Martin Blumenstingl
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='CAFBinCAYWy_VFY8a=AAGpv1+7f5AkWnHk3KDH3fqRMTZfjuNsg@mail.gmail.com' \
--to=martin.blumenstingl@googlemail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=xianwei.zhao@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