From: "Cunhao Lu" <1579567540@qq.com>
To: "Ulf Hansson" <ulf.hansson@oss.qualcomm.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Elaine Zhang" <zhangqing@rock-chips.com>,
"Ulf Hansson" <ulfh@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-rockchip <linux-rockchip@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@vger.kernel.org>,
"Finley Xiao" <finley.xiao@rock-chips.com>
Subject: Re: [PATCH v4 0/2] pmdomain: rockchip: Add RK3572 power domains
Date: Mon, 16 Nov 2026 17:50:15 +0800 [thread overview]
Message-ID: <tencent_E7CC6902FE0862400DA2B35F4B93210D9606@qq.com> (raw)
In-Reply-To: <CAPx+jO_88-xLLiPeE1QPjceCBpBuX0ZXsB=-vVVcGmx_6vnWCA@mail.gmail.com>
Hi,
> There are quite a lot of patches on the rockchip power domain driver
> in the pipe. On my end, I can only try to apply pieces by piece, but
> it would be nice if you could start reviewing each other's patches to
> help coordinate this bit.
>
> Anyway, this series needs to be rebased on top of the latest changes
> that I have queued for next. I will have a look when that's done.
I have rebased this series and its prerequisite power-on rollback
fix [1] onto your latest next branch (6f5c8ec9302c). Both rebased
cleanly, with no conflicts or functional changes.
Should I send new revisions of both (v5 for this series and v2 for
the rollback fix)?
[1] https://patch.msgid.link/20261101-fix-rockchip-pmdomain-power-on-rollback-v1-1-59a45783e33e@qq.com
Best regards,
Cunhao Lu
prev parent reply other threads:[~2026-11-16 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:56 Cunhao Lu via B4 Relay
2026-11-04 8:56 ` [PATCH v4 1/2] dt-bindings: power: " Cunhao Lu via B4 Relay
2026-11-04 8:56 ` [PATCH v4 2/2] pmdomain: " Cunhao Lu via B4 Relay
2026-11-14 10:28 ` [PATCH v4 0/2] " Ulf Hansson
2026-11-16 9:50 ` Cunhao Lu [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=tencent_E7CC6902FE0862400DA2B35F4B93210D9606@qq.com \
--to=1579567540@qq.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.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=robh@kernel.org \
--cc=ulf.hansson@oss.qualcomm.com \
--cc=ulfh@kernel.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
all inboxes | Powered by JetHome®