From: Zhiyong Tao <zhiyong.tao@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: linus.walleij@linaro.org, mark.rutland@arm.com,
matthias.bgg@gmail.com, sean.wang@kernel.org,
srv_heupstream@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 2/4] arm64: dts: mt8183: add pintcrl file
Date: Tue, 26 Mar 2019 10:54:35 +0800 [thread overview]
Message-ID: <1553568875.21970.5.camel@mhfsdcap03> (raw)
In-Reply-To: <20190325193005.GA18114@bogus>
On Mon, 2019-03-25 at 14:30 -0500, Rob Herring wrote:
> On Mon, Mar 25, 2019 at 08:23:00PM +0800, Zhiyong Tao wrote:
> > This patch adds pinctrl file for mt8183.
>
> Still has a typo in the subject.
==>we will change it in next version
>
> >
> > Signed-off-by: Zhiyong Tao <zhiyong.tao@mediatek.com>
> > ---
> > arch/arm64/boot/dts/mediatek/mt8183-pinfunc.h | 1120 +++++++++++++++++++++++++
> > 1 file changed, 1120 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/mediatek/mt8183-pinfunc.h
>
> Add acks/reviewed-bys when posting new versions. This should also be
> called v8 even though a different person sent it.
==>we will add acks/reviewed-bys when posting new versions in nxet
version.
This patch is based on "https://patchwork.kernel.org/patch/10814251/".
If it is based on the patch
"https://patchwork.kernel.org/patch/10814251/", it should called v8.
But I send this patch, we call it v3. Because it it is based on the
patch "https://patchwork.kernel.org/patch/10836969/".
In these v3 patches, we send 4 patches. So we should call 1/4,2/4,3/4 as
v9 in next patch, and call 4/4 patch as v5. is it right?
Thanks.
>
> Rob
>
next prev parent reply other threads:[~2019-03-26 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:22 [PATCH v3 0/4] PINCTRL: Mediatek pinctrl patch on mt8183 Zhiyong Tao
2019-03-25 12:22 ` [PATCH 1/4] dt-bindings: pinctrl: mt8183: add binding document Zhiyong Tao
2019-03-25 12:23 ` [PATCH 2/4] arm64: dts: mt8183: add pintcrl file Zhiyong Tao
2019-03-25 19:30 ` Rob Herring
2019-03-26 2:54 ` Zhiyong Tao [this message]
2019-03-25 12:23 ` [PATCH 3/4] arm64: dts: mt8183: add pintcrl device node Zhiyong Tao
2019-03-25 12:23 ` [PATCH 4/4] pinctrl: add drive for I2C related pins on MT8183 Zhiyong Tao
2019-03-25 18:25 ` Nicolas Boichat
2019-03-26 3:10 ` Zhiyong Tao
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=1553568875.21970.5.camel@mhfsdcap03 \
--to=zhiyong.tao@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=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@kernel.org \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--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;
as well as URLs for NNTP newsgroup(s).