From: CK Hu <ck.hu@mediatek.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Zhiyong Tao <zhiyong.tao@mediatek.com>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Sean Wang <sean.wang@kernel.org>,
<srv_heupstream@mediatek.com>,
Chuanjia Liu <chuanjia.liu@mediatek.com>,
"Biao Huang" <biao.huang@mediatek.com>,
Erin Lo <erin.lo@mediatek.com>, <hui.liu@mediatek.com>,
<seiya.wang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<sin_jieyang@mediatek.com>,
Hongzhou Yang <hongzhou.yang@mediatek.com>,
<sj.huang@mediatek.com>, Rob Herring <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
Sean Wang <sean.wang@mediatek.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
huang eddie <eddie.huang@mediatek.com>, <jg_poxu@mediatek.com>
Subject: Re: [PATCH v4 0/3] Mediatek pinctrl patch on mt8192
Date: Fri, 28 Aug 2020 10:23:54 +0800 [thread overview]
Message-ID: <1598581434.5835.2.camel@mtksdaap41> (raw)
In-Reply-To: <CACRpkdYedyDcnL5DUD33Z2iT1jEJ_W1gvB_a8VaFnNAH1mKgzQ@mail.gmail.com>
Hi, Linus:
On Thu, 2020-08-27 at 10:52 +0200, Linus Walleij wrote:
> On Mon, Aug 17, 2020 at 2:18 AM Zhiyong Tao <zhiyong.tao@mediatek.com> wrote:
>
> > This series includes 3 patches:
> > 1.add pinctrl file on mt8192.
> > 2.add pinctrl binding document on mt8192.
> > 3.add pinctrl driver on MT8192.
>
> Patches applied for v5.10!
I does not see these patches in your tree [1], have you applied them? I
would like to pick these patches from your tree.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/
Regards,
CK
> Thanks!
> Linus Walleij
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-08-28 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 0:16 [PATCH v4 0/3] Mediatek pinctrl patch on mt8192 Zhiyong Tao
2020-08-17 0:17 ` [PATCH v4 1/3] dt-bindings: pinctrl: mt8192: add pinctrl file Zhiyong Tao
2020-08-17 0:17 ` [PATCH v4 2/3] dt-bindings: pinctrl: mt8192: add binding document Zhiyong Tao
2020-08-25 2:26 ` Rob Herring
2020-08-17 0:17 ` [PATCH v4 3/3] pinctrl: add pinctrl driver on mt8192 Zhiyong Tao
2020-08-27 8:52 ` [PATCH v4 0/3] Mediatek pinctrl patch " Linus Walleij
2020-08-28 2:23 ` CK Hu [this message]
2020-08-28 14:38 ` Linus Walleij
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=1598581434.5835.2.camel@mtksdaap41 \
--to=ck.hu@mediatek.com \
--cc=biao.huang@mediatek.com \
--cc=chuanjia.liu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=hongzhou.yang@mediatek.com \
--cc=hui.liu@mediatek.com \
--cc=jg_poxu@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=seiya.wang@mediatek.com \
--cc=sin_jieyang@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=zhiyong.tao@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).