From: Wolfram Sang <wsa@the-dreams.de>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, tglx@linutronix.de,
jason@lakedaemon.net, marc.zyngier@arm.com,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] dt-bindings: i2c-mtk: Add mt7623 binding
Date: Wed, 7 Jun 2017 18:15:13 +0200 [thread overview]
Message-ID: <20170607161513.zjehj5nirn2fx3eg@ninjato> (raw)
In-Reply-To: <20170522094021.7837-4-matthias.bgg@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
On Mon, May 22, 2017 at 11:40:21AM +0200, Matthias Brugger wrote:
> The mt7623 dtsi has support for the i2c block, but this is not documented.
> Add the documentation for SoC mt7623 to de description.
>
> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
Acked-by: Wolfram Sang <wsa@the-dreams.de>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-07 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:40 [PATCH 1/4] dt-bindings: mtk-sysirq: Correct bindings for supported SoCs Matthias Brugger
2017-05-22 9:40 ` [PATCH 2/4] dt-bindings: i2c-mt6577: Rename file to reflect bindings Matthias Brugger
[not found] ` <20170522094021.7837-2-matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-07 16:15 ` Wolfram Sang
2017-05-22 9:40 ` [PATCH 3/4] dt-bindigns: i2c-mtk: Delete bindings Matthias Brugger
2017-06-07 16:15 ` Wolfram Sang
2017-05-22 9:40 ` [PATCH 4/4] dt-bindings: i2c-mtk: Add mt7623 binding Matthias Brugger
2017-06-07 16:15 ` Wolfram Sang [this message]
[not found] ` <20170522094021.7837-1-matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-30 23:13 ` [PATCH 1/4] dt-bindings: mtk-sysirq: Correct bindings for supported SoCs Rob Herring
2017-05-31 12:05 ` 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=20170607161513.zjehj5nirn2fx3eg@ninjato \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--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=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).