From: Florian Fainelli <f.fainelli@gmail.com>
To: arm@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
arnd@arndb.de, Kevin Hilman <khilman@kernel.org>,
bcm-kernel-feedback-list@broadcom.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] Broadcom devicetree fixes for 5.2
Date: Mon, 20 May 2019 11:26:46 -0700 [thread overview]
Message-ID: <20190520182648.1063-1-f.fainelli@gmail.com> (raw)
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.2/devicetree-fixes
for you to fetch changes up to e8bd76dccd792b371a934336c3e7d8c389755d9f:
ARM: dts: bcm: Add missing device_type = "memory" property (2019-05-20 09:29:47 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
5.2-rc1, please pull the following:
- Florian fixes the remaining Broadcom DTS files to have a valid
device_type = "memory" property which was missed during the removal of
skeleton.dtsi
----------------------------------------------------------------
Florian Fainelli (1):
ARM: dts: bcm: Add missing device_type = "memory" property
arch/arm/boot/dts/bcm4708-asus-rt-ac56u.dts | 1 +
arch/arm/boot/dts/bcm4708-asus-rt-ac68u.dts | 1 +
arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dts | 1 +
arch/arm/boot/dts/bcm4708-linksys-ea6300-v1.dts | 1 +
arch/arm/boot/dts/bcm4708-linksys-ea6500-v2.dts | 1 +
arch/arm/boot/dts/bcm4708-luxul-xap-1510.dts | 1 +
arch/arm/boot/dts/bcm4708-luxul-xwc-1000.dts | 1 +
arch/arm/boot/dts/bcm4708-netgear-r6250.dts | 1 +
arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dts | 1 +
arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dts | 1 +
arch/arm/boot/dts/bcm4709-asus-rt-ac87u.dts | 1 +
arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dts | 1 +
arch/arm/boot/dts/bcm4709-linksys-ea9200.dts | 1 +
arch/arm/boot/dts/bcm4709-netgear-r7000.dts | 1 +
arch/arm/boot/dts/bcm4709-netgear-r8000.dts | 1 +
arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dts | 1 +
arch/arm/boot/dts/bcm47094-phicomm-k3.dts | 1 +
arch/arm/boot/dts/bcm94708.dts | 1 +
arch/arm/boot/dts/bcm94709.dts | 1 +
arch/arm/boot/dts/bcm963138dvt.dts | 1 +
20 files changed, 20 insertions(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-05-20 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 18:26 Florian Fainelli [this message]
2019-05-20 18:26 ` [GIT PULL 2/3] Broadcom drivers fixes for 5.2 Florian Fainelli
2019-06-16 20:25 ` Olof Johansson
2019-05-20 18:26 ` [GIT PULL 3/3] Broadcom maintainers-arm64 " Florian Fainelli
2019-06-16 20:25 ` Olof Johansson
2019-05-28 22:34 ` [GIT PULL 1/3] Broadcom devicetree " Florian Fainelli
2019-06-05 19:02 ` Florian Fainelli
2019-06-16 20:29 ` Olof Johansson
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=20190520182648.1063-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
/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).