From: Wolfram Sang <wsa@the-dreams.de>
To: Kewei Xu <kewei.xu@mediatek.com>
Cc: matthias.bgg@gmail.com, robh+dt@kernel.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
srv_heupstream@mediatek.com, leilk.liu@mediatek.com,
qii.wang@mediatek.com, liguo.zhang@mediatek.com,
caiyu.chen@mediatek.com, housong.zhang@mediatek.com,
yuhan.wei@mediatek.com, ryan-jh.yu@mediatek.com
Subject: Re: [v2 0/2] add i2c support for mt8186
Date: Fri, 28 Jan 2022 22:46:03 +0100 [thread overview]
Message-ID: <YfRkG7KdAMD7FiuY@shikoro> (raw)
In-Reply-To: <20220125110413.18988-1-kewei.xu@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
On Tue, Jan 25, 2022 at 07:04:11PM +0800, Kewei Xu wrote:
> V1:
> Add i2c compatible for MT8186. Compare to MT8192 i2c controller,
> MT8186 doesn't need handshake signal with apdma.
A description of what has changed in v2 would have been helpful. Please
add it next time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-01-28 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 11:04 [v2 0/2] add i2c support for mt8186 Kewei Xu
2022-01-25 11:04 ` [v2 1/2] dt-bindings: i2c: update bindings for MT8186 SoC Kewei Xu
2022-01-25 11:26 ` Qii Wang
2022-01-28 21:46 ` Wolfram Sang
2022-02-07 2:53 ` Kewei Xu
2022-01-25 11:04 ` [v2 2/2] i2c: mediatek: Add i2c compatible for Mediatek MT8186 Kewei Xu
2022-01-25 11:27 ` Qii Wang
2022-01-28 21:46 ` Wolfram Sang
2022-01-28 21:46 ` Wolfram Sang [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=YfRkG7KdAMD7FiuY@shikoro \
--to=wsa@the-dreams.de \
--cc=caiyu.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=housong.zhang@mediatek.com \
--cc=kewei.xu@mediatek.com \
--cc=leilk.liu@mediatek.com \
--cc=liguo.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=qii.wang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=ryan-jh.yu@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=yuhan.wei@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).