From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: "Otto Pflüger" <otto.pflueger@abscue.de>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Orson Zhai" <orsonzhai@gmail.com>,
"Chunyan Zhang" <zhang.lyra@gmail.com>,
"Lee Jones" <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] regulator: Add regulator driver for Unisoc SC2730 PMIC
Date: Tue, 24 Feb 2026 14:28:49 +0800 [thread overview]
Message-ID: <f48b9c3c-4e72-4169-95e5-989f4e9f0c42@linux.alibaba.com> (raw)
In-Reply-To: <20260220-sc2730-regulators-v1-3-3f2bbc9ecf14@abscue.de>
On 2/21/26 1:01 AM, Otto Pflüger wrote:
> Add a regulator driver for the Spreadtrum/Unisoc SC2730 PMIC, used
> e.g. with the UMS512 and UMS9230 SoCs. This version of the driver is
> based on a downstream driver provided by Unisoc [1] and the existing
> SC2731 driver.
>
> Signed-off-by: Otto Pflüger <otto.pflueger@abscue.de>
Please add the original author’s SoB tag. The code looks good to me. Thanks.
prev parent reply other threads:[~2026-02-24 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 17:01 [PATCH 0/3] regulator: Add support for Unisoc SC2730 PMIC regulators Otto Pflüger
2026-02-20 17:01 ` [PATCH 1/3] dt-bindings: regulator: Document Unisoc SC2730 PMIC bindings Otto Pflüger
2026-02-21 10:52 ` Krzysztof Kozlowski
2026-02-21 13:02 ` Otto Pflüger
2026-02-21 13:17 ` Krzysztof Kozlowski
2026-02-20 17:01 ` [PATCH 2/3] dt-bindings: mfd: sprd,sc2731: Reference sprd,sc2730-regulator bindings Otto Pflüger
2026-02-21 10:50 ` Krzysztof Kozlowski
2026-02-20 17:01 ` [PATCH 3/3] regulator: Add regulator driver for Unisoc SC2730 PMIC Otto Pflüger
2026-02-24 6:28 ` Baolin Wang [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=f48b9c3c-4e72-4169-95e5-989f4e9f0c42@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=otto.pflueger@abscue.de \
--cc=robh@kernel.org \
--cc=zhang.lyra@gmail.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