From: Mark Brown <broonie@kernel.org>
To: Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Fei Shao <fshao@chromium.org>, Ran Bi <ran.bi@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org, srv_heupstream@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v6 7/8] regulator: mt6359: Add support for MT6359P regulator
Date: Tue, 16 Mar 2021 17:52:25 +0000 [thread overview]
Message-ID: <20210316175225.GD4309@sirena.org.uk> (raw)
In-Reply-To: <1615829757-3223-8-git-send-email-hsin-hsiung.wang@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
On Tue, Mar 16, 2021 at 01:35:56AM +0800, Hsin-Hsiung Wang wrote:
> The MT6359P is a eco version for MT6359 regulator.
> We add support based on MT6359 regulator driver.
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-16 17:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:35 [PATCH v6 0/8] Add Support for MediaTek PMIC MT6359 Hsin-Hsiung Wang
2021-03-15 17:35 ` [PATCH v6 1/8] mfd: mt6358: refine interrupt code Hsin-Hsiung Wang
2021-03-15 17:35 ` [PATCH v6 2/8] rtc: mt6397: refine RTC_TC_MTH Hsin-Hsiung Wang
2021-03-15 17:35 ` [PATCH v6 3/8] dt-bindings: mfd: Add compatible for the MediaTek MT6359 PMIC Hsin-Hsiung Wang
2021-03-15 17:35 ` [PATCH v6 4/8] dt-bindings: regulator: Add document for MT6359 regulator Hsin-Hsiung Wang
2021-03-16 17:54 ` Rob Herring
2021-03-16 21:28 ` Rob Herring
2021-03-17 6:01 ` Hsin-hsiung Wang
2021-03-29 11:13 ` Hsin-hsiung Wang
2021-03-15 17:35 ` [PATCH v6 5/8] mfd: Add support for the MediaTek MT6359 PMIC Hsin-Hsiung Wang
2021-03-15 17:35 ` [PATCH v6 6/8] regulator: mt6359: Add support for MT6359 regulator Hsin-Hsiung Wang
2021-03-16 17:52 ` Mark Brown
2021-03-15 17:35 ` [PATCH v6 7/8] regulator: mt6359: Add support for MT6359P regulator Hsin-Hsiung Wang
2021-03-16 17:52 ` Mark Brown [this message]
2021-03-15 17:35 ` [PATCH v6 8/8] arm64: dts: mt6359: add PMIC MT6359 related nodes Hsin-Hsiung Wang
2021-03-29 15:24 ` Matthias Brugger
2021-03-30 2:40 ` Hsin-hsiung Wang
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=20210316175225.GD4309@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=eddie.huang@mediatek.com \
--cc=fshao@chromium.org \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ran.bi@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=yingjoe.chen@mediatek.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).