From: "Heiko Stübner" <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Kever Yang <kever.yang@rock-chips.com>,
Finley Xiao <finley.xiao@rock-chips.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-pm@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v3 2/2] soc: rockchip: power-domain: add power domain support for rk3562
Date: Thu, 27 Feb 2025 14:19:49 +0100 [thread overview]
Message-ID: <2307779.KTMopqUuYO@diego> (raw)
In-Reply-To: <20250227105957.2341107-3-kever.yang@rock-chips.com>
Am Donnerstag, 27. Februar 2025, 11:59:57 MEZ schrieb Kever Yang:
> This driver is modified to support RK3562 SoC.
> Add support to ungate clk.
> Add support to shut down memory for rk3562.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
forgot one thing, patch author doesn't match.
You have a first Signed-off-by from Finley, so the patch author
should be the same - similar to how the binding patch already is?
Heiko
prev parent reply other threads:[~2025-02-27 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 10:59 [PATCH v3 0/2] rockchip: Add rk3562 power domain support Kever Yang
2025-02-27 10:59 ` [PATCH v3 1/2] dt-bindings: power: rockchip: Add support for RK3562 SoC Kever Yang
2025-02-27 13:14 ` Heiko Stübner
2025-02-27 15:29 ` Krzysztof Kozlowski
2025-02-27 10:59 ` [PATCH v3 2/2] soc: rockchip: power-domain: add power domain support for rk3562 Kever Yang
2025-02-27 13:18 ` Heiko Stübner
2025-02-27 13:19 ` Heiko Stübner [this message]
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=2307779.KTMopqUuYO@diego \
--to=heiko@sntech.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=detlev.casanova@collabora.com \
--cc=finley.xiao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ulf.hansson@linaro.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).