From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rob Herring <robh@kernel.org>, sean.wang@mediatek.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: mediatek: add bindings for MediaTek MT7622 SoC
Date: Thu, 8 Jun 2017 16:37:11 +0200 [thread overview]
Message-ID: <dc04ea44-4f4c-a914-2f92-266b3d11eb54@gmail.com> (raw)
In-Reply-To: <20170607213028.xsbgwwjgbgghk3vg@rob-hp-laptop>
On 07/06/17 23:30, Rob Herring wrote:
> On Thu, Jun 01, 2017 at 01:28:59AM +0800, sean.wang@mediatek.com wrote:
>> From: Sean Wang <sean.wang@mediatek.com>
>>
>> This adds dt-binding documentation for MediaTek MT7622 SoC
>> which currently only includes basic items such as ARM CPU,
>> MediaTek SYSIRQ and UART.
>>
>> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
>> ---
>> Documentation/devicetree/bindings/arm/mediatek.txt | 4 ++++
>> .../devicetree/bindings/interrupt-controller/mediatek,sysirq.txt | 3 ++-
>> Documentation/devicetree/bindings/serial/mtk-uart.txt | 1 +
>> 3 files changed, 7 insertions(+), 1 deletion(-)
>
> Acked-by: Rob Herring <robh@kernel.org>
>
Pushed this one to v4.12-next/dts64
Thanks,
Matthias
next prev parent reply other threads:[~2017-06-08 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 17:28 [PATCH v3 0/4] Add Basic SoC support for MT7622 sean.wang
2017-05-31 17:28 ` [PATCH v3 1/3] dt-bindings: mediatek: add bindings for MediaTek MT7622 SoC sean.wang
2017-06-07 21:30 ` Rob Herring
2017-06-08 14:37 ` Matthias Brugger [this message]
2017-05-31 17:29 ` [PATCH v3 2/3] arm64: dts: mt7622: add basic nodes to the mt7622.dtsi file sean.wang
2017-06-08 13:52 ` Matthias Brugger
2017-06-08 16:07 ` Sean Wang
2017-06-08 16:24 ` Matthias Brugger
2017-05-31 17:29 ` [PATCH v3 3/3] arm64: dts: mt7622: add dts file for MT7622 reference board variant 1 sean.wang
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=dc04ea44-4f4c-a914-2f92-266b3d11eb54@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=sean.wang@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
Powered by JetHome