From: Rob Herring <robh@kernel.org>
Cc: robh+dt@kernel.org, linus.walleij@linaro.org,
mark.rutland@arm.com, matthias.bgg@gmail.com,
sean.wang@kernel.org, srv_heupstream@mediatek.com,
zhiyong.tao@mediatek.com, hui.liu@mediatek.com,
eddie.huang@mediatek.com, chuanjia.liu@mediatek.com,
biao.huang@mediatek.com, hongzhou.yang@mediatek.com,
erin.lo@mediatek.com, sean.wang@mediatek.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH RESEND v3 1/4] dt-bindings: pinctrl: mt8183: add binding document
Date: Thu, 28 Mar 2019 13:31:44 -0500 [thread overview]
Message-ID: <20190328183144.GA7855@bogus> (raw)
In-Reply-To: <20190325124137.6117-2-zhiyong.tao@mediatek.com>
On Mon, 25 Mar 2019 20:41:34 +0800, Zhiyong Tao wrote:
> The commit adds mt8183 compatible node in binding document.
>
> Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
> ---
> .../devicetree/bindings/pinctrl/pinctrl-mt8183.txt | 132 +++++++++++++++++++++
> 1 file changed, 132 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8183.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-03-28 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:41 [PATCH v3 RESEND 0/4] PINCTRL: Mediatek pinctrl patch on mt8183 Zhiyong Tao
2019-03-25 12:41 ` [PATCH RESEND v3 1/4] dt-bindings: pinctrl: mt8183: add binding document Zhiyong Tao
2019-03-28 18:31 ` Rob Herring [this message]
2019-03-25 12:41 ` [PATCH RESEND v3 2/4] arm64: dts: mt8183: add pintcrl file Zhiyong Tao
2019-03-25 12:41 ` [PATCH RESEND v3 3/4] arm64: dts: mt8183: add pintcrl device node Zhiyong Tao
2019-03-25 18:17 ` Nicolas Boichat
2019-03-26 2:55 ` Zhiyong Tao
2019-03-25 12:41 ` [PATCH RESEND v3 4/4] pinctrl: add drive for I2C related pins on MT8183 Zhiyong Tao
2019-04-16 8:08 ` Matthias Brugger
2019-04-23 10:59 ` Linus Walleij
2019-04-23 14:10 ` Matthias Brugger
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=20190328183144.GA7855@bogus \
--to=robh@kernel.org \
--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=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=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).