From: Matthias Brugger <matthias.bgg@gmail.com>
To: YT Shen <yt.shen@mediatek.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, srv_heupstream@mediatek.com
Subject: Re: [PATCH 0/8] add dts nodes to MT2712 SoC
Date: Wed, 9 Jan 2019 18:20:47 +0100 [thread overview]
Message-ID: <98d0fefa-6331-da37-414e-3639ff4df97c@gmail.com> (raw)
In-Reply-To: <1543836962-18293-1-git-send-email-yt.shen@mediatek.com>
On 03/12/2018 12:35, YT Shen wrote:
> This patch series based on v4.20-rc1, include MT2712 usb/iommu/smi/i2c/spi/pwm/mmc/nand/pcie device nodes
>
> Chunfeng Yun (1):
> arm64: dts: Add USB3 related nodes for MT2712
>
> Honghui Zhang (1):
> arm64: dts: add pcie nodes for MT2712
>
> YT Shen (6):
> arm64: dts: add iommu/smi nodes for MT2712
> arm64: dts: add i2c nodes for MT2712
> arm64: dts: add spi nodes for MT2712
> arm64: dts: add pwm nodes for MT2712
> arm64: dts: add mmc nodes for MT2712
> arm64: dts: add nand nodes for MT2712
>
All pushed to v5.0-next/dts64
Thanks,
Matthias
> arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 98 +++++
> arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 555 ++++++++++++++++++++++++++++
> 2 files changed, 653 insertions(+)
>
prev parent reply other threads:[~2019-01-09 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 11:35 YT Shen
2018-12-03 11:35 ` [PATCH 1/8] arm64: dts: Add USB3 related nodes for MT2712 YT Shen
2018-12-03 11:35 ` [PATCH 2/8] arm64: dts: add iommu/smi " YT Shen
2018-12-03 11:35 ` [PATCH 3/8] arm64: dts: add i2c " YT Shen
2018-12-03 11:35 ` [PATCH 4/8] arm64: dts: add spi " YT Shen
2018-12-03 11:35 ` [PATCH 5/8] arm64: dts: add pwm " YT Shen
2018-12-03 11:36 ` [PATCH 6/8] arm64: dts: add mmc " YT Shen
2018-12-03 11:36 ` [PATCH 7/8] arm64: dts: add nand " YT Shen
2018-12-03 11:36 ` [PATCH 8/8] arm64: dts: add pcie " YT Shen
2019-01-09 17:20 ` Matthias Brugger [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=98d0fefa-6331-da37-414e-3639ff4df97c@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+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=yt.shen@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