From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] arm: dts: Add Mediatek MT2701 i2c device node
Date: Tue, 13 Jun 2017 11:36:52 +0200 [thread overview]
Message-ID: <dbfcfd5b-8812-8df2-40dc-42e889577c9a@gmail.com> (raw)
In-Reply-To: <1497268468.930.26.camel@mhfsdcap03>
On 12/06/17 13:54, Jun Gao wrote:
> On Fri, 2017-05-26 at 15:35 +0800, Jun Gao wrote:
>> From: Jun Gao <jun.gao@mediatek.com>
>>
>> Add MT2701 i2c device node.
>>
>> Signed-off-by: Jun Gao <jun.gao@mediatek.com>
>> ---
>> arch/arm/boot/dts/mt2701-evb.dts | 42 ++++++++++++++++++++++++++++++++++++++++
>> arch/arm/boot/dts/mt2701.dtsi | 42 ++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 84 insertions(+)
[...]
>
> Dear Matthias,
>
> Could you take this patch together with
> [PATCH v4 1/2]dt-bindings: i2c: Add Mediatek MT2701 i2c binding ?
>
> Thanks!
>
They are both included in the pull request I send [1] [2], or do I miss
something?
Regards,
Matthias
[1]
https://github.com/mbgg/linux-mediatek/commit/729b7f8dbdaff270c53052897ea06486221a49a2
[2]
https://github.com/mbgg/linux-mediatek/commit/c6c301d3ff7531894257acc4f4a73928a109bda1
next prev parent reply other threads:[~2017-06-13 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 7:35 [PATCH v4 0/2] Add i2c dt-binding and device node for Mediatek MT2701 Soc Jun Gao
2017-05-26 7:35 ` [PATCH v4 1/2] dt-bindings: i2c: Add Mediatek MT2701 i2c binding Jun Gao
2017-05-29 15:30 ` Matthias Brugger
2017-05-30 21:38 ` Rob Herring
2017-05-31 2:24 ` Jun Gao
2017-05-31 12:05 ` Matthias Brugger
2017-05-26 7:35 ` [PATCH v4 2/2] arm: dts: Add Mediatek MT2701 i2c device node Jun Gao
2017-06-12 11:54 ` Jun Gao
2017-06-13 9:36 ` Matthias Brugger [this message]
2017-06-13 10:24 ` Jun Gao
2017-06-13 12:52 ` Matthias Brugger
2017-06-13 13:23 ` Jun Gao
2017-06-13 13:45 ` Matthias Brugger
2017-06-14 1:11 ` Jun Gao
2017-06-14 9:24 ` Matthias Brugger
2017-06-14 9:43 ` Jun Gao
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=dbfcfd5b-8812-8df2-40dc-42e889577c9a@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).