From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kever Yang <kever.yang@rock-chips.com>, heiko@sntech.de
Cc: linux-rockchip@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Detlev Casanova <detlev.casanova@collabora.com>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Elaine Zhang <zhangqing@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: power: rockchip: Add support for RK3562 SoC
Date: Thu, 27 Feb 2025 16:29:47 +0100 [thread overview]
Message-ID: <fbe35002-9a0d-4dcd-b195-4c45aabb2098@kernel.org> (raw)
In-Reply-To: <20250227105957.2341107-2-kever.yang@rock-chips.com>
On 27/02/2025 11:59, Kever Yang wrote:
> From: Finley Xiao <finley.xiao@rock-chips.com>
>
> According to a description from TRM, add all the power domains.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v3:
> - squash the header file and the binding document
> - Update license
>
> Changes in v2:
> - rename to rockchip,rk3562-power.h
We usually expect filename matching compatible. Any particular reason to
have different one?
I don't see here links to previous versions and I cannot find it on
lore, so not sure what feedback did you get at v1.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-02-27 15:29 UTC|newest]
Thread overview: 4+ 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 [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=fbe35002-9a0d-4dcd-b195-4c45aabb2098@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=zhangqing@rock-chips.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).