From: James Lo <james.lo@mediatek.com>
To: Stephen Boyd <sboyd@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v16 0/4] Add SPMI support for Mediatek SoC IC
Date: Fri, 10 Dec 2021 16:08:37 +0800 [thread overview]
Message-ID: <a8275c2ee2a7fad619605b433d61077a03ed4796.camel@mediatek.com> (raw)
In-Reply-To: <20211210021215.0EE19C004DD@smtp.kernel.org>
On Thu, 2021-12-09 at 18:12 -0800, Stephen Boyd wrote:
> Quoting James Lo (2021-11-18 19:46:09)
> > This series adds support for new SoC MT6873/MT8192/MT8195 to the
> > spmi driver.
> > This series is based on Chun-Jie's patches[1].
> >
> > [1]
> > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=521655__;!!CTRNKA9wMg0ARbw!ycJplySfH-hTtYCIdjkF0VvfKgtq2B1NeOaBAOw5GU05898X6B7FN21KLkKTZiPC$
> >
>
> This isn't needed though right? I've picked these four patches up
> into
> spmi-next.
Yes. You are right.
It's just for notice the patch dependency.
Many Thanks!
prev parent reply other threads:[~2021-12-10 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 3:46 James Lo
2021-11-19 3:46 ` [PATCH v16 1/4] dt-bindings: spmi: remove the constraint of reg property James Lo
2021-11-19 3:46 ` [PATCH v16 2/4] dt-bindings: spmi: document binding for the Mediatek SPMI controller James Lo
2021-11-19 3:46 ` [PATCH v16 3/4] spmi: mediatek: Add support for MT6873/8192 James Lo
2021-11-19 3:46 ` [PATCH v16 4/4] spmi: mediatek: Add support for MT8195 James Lo
2021-12-10 2:12 ` [PATCH v16 0/4] Add SPMI support for Mediatek SoC IC Stephen Boyd
2021-12-10 8:08 ` James Lo [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=a8275c2ee2a7fad619605b433d61077a03ed4796.camel@mediatek.com \
--to=james.lo@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@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
all inboxes | Powered by JetHome®