linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Johnson Wang <johnson.wang@mediatek.com>, robh+dt@kernel.org
Cc: angelogioacchino.delregno@collabora.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v3 0/2] Add PMIC wrapper support for Mediatek MT8186 SoC IC
Date: Tue, 1 Mar 2022 08:52:33 +0100	[thread overview]
Message-ID: <95f33dbd-4388-20ec-1e4c-ac323de9d18a@gmail.com> (raw)
In-Reply-To: <20220207083034.15327-1-johnson.wang@mediatek.com>



On 07/02/2022 09:30, Johnson Wang wrote:
> This series add PMIC wrapper support for Mediatek MT8186 SoC IC
> 
> Changes since v2:
> - Replace meaningless suffix _V2 with _MT8186 because
>    these IPs are only for MT8186 SoC.
> - Remove not used capability PWRAP_CAP_MONITOR_V2.
> 
> Changes since v1:
> - Fix the conditional logic in pwrap_probe() function.
> 
> Johnson Wang (2):
>    soc: mediatek: pwrap: add pwrap driver for MT8186 SoC
>    dt-bindings: mediatek: add compatible for MT8186 pwrap
> 
>   .../bindings/soc/mediatek/pwrap.txt           |  1 +
>   drivers/soc/mediatek/mtk-pmic-wrap.c          | 71 +++++++++++++++++++
>   2 files changed, 72 insertions(+)
> 

Series applied, thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2022-03-01  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  8:30 [PATCH v3 0/2] Add PMIC wrapper support for Mediatek MT8186 SoC IC Johnson Wang
2022-02-07  8:30 ` [PATCH v3 1/2] soc: mediatek: pwrap: add pwrap driver for MT8186 SoC Johnson Wang
2022-02-07  8:30 ` [PATCH v3 2/2] dt-bindings: mediatek: add compatible for MT8186 pwrap Johnson Wang
2022-03-01  7:52 ` Matthias Brugger [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=95f33dbd-4388-20ec-1e4c-ac323de9d18a@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=johnson.wang@mediatek.com \
    --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).