From: Wolfram Sang <wsa@the-dreams.de>
To: Jun Gao <jun.gao@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
srv_heupstream@mediatek.com, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v4 2/3] dt-bindings: i2c: Add MediaTek MT7622 i2c binding
Date: Sun, 27 Aug 2017 15:31:47 +0200 [thread overview]
Message-ID: <20170827133147.gv3mjvz3buodta26@ninjato> (raw)
In-Reply-To: <1503286614-17670-3-git-send-email-jun.gao@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
On Mon, Aug 21, 2017 at 11:36:53AM +0800, Jun Gao wrote:
> From: Jun Gao <jun.gao@mediatek.com>
>
> Add MT7622 i2c binding to binding file. Compare to MT8173 i2c
> controller, MT7622 limits message numbers to 255, and does not
> support 4GB DMA mode.
>
> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/3] dt-bindings: i2c: Add MediaTek MT7622 i2c binding
Date: Sun, 27 Aug 2017 15:31:47 +0200 [thread overview]
Message-ID: <20170827133147.gv3mjvz3buodta26@ninjato> (raw)
In-Reply-To: <1503286614-17670-3-git-send-email-jun.gao@mediatek.com>
On Mon, Aug 21, 2017 at 11:36:53AM +0800, Jun Gao wrote:
> From: Jun Gao <jun.gao@mediatek.com>
>
> Add MT7622 i2c binding to binding file. Compare to MT8173 i2c
> controller, MT7622 limits message numbers to 255, and does not
> support 4GB DMA mode.
>
> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
Applied to for-next, thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170827/71d60c52/attachment-0001.sig>
next prev parent reply other threads:[~2017-08-27 13:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 3:36 [PATCH v4 0/3] Add i2c dt-binding and compatible for Mediatek MT7622 SoC Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-21 3:36 ` [PATCH v4 1/3] dt-bindings: i2c: modify information formats Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-23 0:36 ` Rob Herring
2017-08-23 0:36 ` Rob Herring
2017-08-27 13:31 ` Wolfram Sang
2017-08-27 13:31 ` Wolfram Sang
2017-08-27 13:31 ` Wolfram Sang
2017-08-21 3:36 ` [PATCH v4 2/3] dt-bindings: i2c: Add MediaTek MT7622 i2c binding Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-23 0:36 ` Rob Herring
2017-08-23 0:36 ` Rob Herring
2017-08-23 0:36 ` Rob Herring
2017-08-27 13:31 ` Wolfram Sang [this message]
2017-08-27 13:31 ` Wolfram Sang
2017-08-21 3:36 ` [PATCH v4 3/3] i2c: mediatek: Add i2c compatible for MediaTek MT7622 Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-21 3:36 ` Jun Gao
2017-08-27 13:31 ` Wolfram Sang
2017-08-27 13:31 ` Wolfram Sang
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=20170827133147.gv3mjvz3buodta26@ninjato \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=jun.gao@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.