From: Mark Brown <broonie@kernel.org>
To: Johnson Wang <johnson.wang@mediatek.com>
Cc: lee.jones@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH 2/4] regulator: mt6366: Add support for MT6366 regulator
Date: Thu, 6 Jan 2022 12:59:15 +0000 [thread overview]
Message-ID: <Ydbno0JM8YP9NhNh@sirena.org.uk> (raw)
In-Reply-To: <20220106065407.16036-3-johnson.wang@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
On Thu, Jan 06, 2022 at 02:54:05PM +0800, Johnson Wang wrote:
> The MT6366 is a regulator found on boards based on MediaTek MT8186 and
> probably other SoCs. It is a so called pmic and connects as a slave to
> SoC using SPI, wrapped inside the pmic-wrapper.
Reviwed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-06 12:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 6:54 [PATCH 0/4] Add Support for MediaTek PMIC MT6366 Johnson Wang
2022-01-06 6:54 ` [PATCH 1/4] mfd: Add support for the MediaTek MT6366 PMIC Johnson Wang
2022-02-07 7:04 ` Johnson Wang
2022-02-14 13:39 ` Lee Jones
2022-02-23 8:28 ` Johnson Wang
2022-02-23 9:02 ` Lee Jones
2022-01-06 6:54 ` [PATCH 2/4] regulator: mt6366: Add support for MT6366 regulator Johnson Wang
2022-01-06 12:59 ` Mark Brown [this message]
2022-02-23 9:58 ` Johnson Wang
2022-01-06 6:54 ` [PATCH 3/4] dt-bindings: mfd: Add compatible for the MediaTek MT6366 PMIC Johnson Wang
2022-01-12 1:44 ` Rob Herring
2022-02-14 13:39 ` Lee Jones
2022-01-06 6:54 ` [PATCH 4/4] dt-bindings: regulator: Add MT6358 regulators Johnson Wang
2022-01-06 13:09 ` Mark Brown
2022-01-12 1:45 ` Rob Herring
2022-03-03 8:18 ` Fei Shao
2022-03-08 8:28 ` [GIT PULL - FAO MARK BROWN]: Immutable branch for MediaTek MT6366 due for the v5.18 merge window Lee Jones
2022-03-08 12:49 ` Mark Brown
2022-03-08 13:09 ` Lee Jones
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=Ydbno0JM8YP9NhNh@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=johnson.wang@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.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).