From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Hui Liu <hui.liu@mediatek.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
wenst@google.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
jianguo.zhang@mediatek.com, zhiyong.tao@mediatek.com,
sean.wang@mediatek.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] MediaTek pinctrl patch on mt8188
Date: Thu, 25 Aug 2022 11:13:50 -0400 [thread overview]
Message-ID: <20220825151350.mbovhtvcgnf6shwd@notapiano> (raw)
In-Reply-To: <CACRpkdbGjbd9Q9Chcnnc=3nD3XALsCdk7dz9mT3BfJdZs62xjA@mail.gmail.com>
On Thu, Aug 25, 2022 at 02:54:32PM +0200, Linus Walleij wrote:
> On Thu, Aug 18, 2022 at 9:50 AM Hui Liu <hui.liu@mediatek.com> wrote:
>
> > Changes in patch v6:
> > 1.Update driver file's coding style.
>
> No further comments on this version so patch applied. If Sean
> has further comments they can be addressed in-tree.
>
> Nicolas: thanks for helping out with review!
Sure! Glad to help.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-08-25 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 7:50 [PATCH v6 0/2] MediaTek pinctrl patch on mt8188 Hui Liu
2022-08-18 7:50 ` [PATCH v6 1/2] dt-bindings: pinctrl: mediatek: add support for mt8188 Hui Liu
2022-08-23 21:21 ` Nícolas F. R. A. Prado
[not found] ` <20220818075012.20880-3-hui.liu@mediatek.com>
2022-08-23 21:11 ` [PATCH v6 2/2] pinctrl: mediatek: add mt8188 driver Nícolas F. R. A. Prado
2022-08-25 12:54 ` [PATCH v6 0/2] MediaTek pinctrl patch on mt8188 Linus Walleij
2022-08-25 15:13 ` Nícolas F. R. A. Prado [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=20220825151350.mbovhtvcgnf6shwd@notapiano \
--to=nfraprado@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hui.liu@mediatek.com \
--cc=jianguo.zhang@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=wenst@google.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