From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/1] Broadcom devicetree fixes for 4.15
Date: Mon, 27 Nov 2017 12:08:17 -0800 [thread overview]
Message-ID: <20171127200817.32647-1-f.fainelli@gmail.com> (raw)
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.15/devicetree-fixes-1
for you to fetch changes up to babd8a3e31fbb0abb4c37ee3548974732080b996:
Merge tag 'bcm2835-dt-next-fixes-2017-11-15' into devicetree/fixes (2017-11-27 11:28:23 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for 4.15,
please pull the following:
- Stefan provides a fix for the BCM2835 (Raspberry Pi) to fix warnings about
missing "#phy-cells" properties
- Florian provides two fixes for Nortsthar Plus, one that uses the correct
interrupt specifiers for the timer/watchdog and one that disables SATA
on BCM9582**HR boards since that leads to unidentified hangs right now
----------------------------------------------------------------
Florian Fainelli (3):
ARM: dts: NSP: Disable AHCI controller for HR NSP boards
ARM: dts: NSP: Fix PPI interrupt types
Merge tag 'bcm2835-dt-next-fixes-2017-11-15' into devicetree/fixes
Stefan Wahren (1):
ARM: dts: bcm283x: Fix DTC warnings about missing phy-cells
arch/arm/boot/dts/bcm-nsp.dtsi | 4 ++--
arch/arm/boot/dts/bcm283x.dtsi | 1 +
arch/arm/boot/dts/bcm958623hr.dts | 4 ----
arch/arm/boot/dts/bcm958625hr.dts | 4 ----
4 files changed, 3 insertions(+), 10 deletions(-)
next reply other threads:[~2017-11-27 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 20:08 Florian Fainelli [this message]
2017-12-03 0:57 ` [GIT PULL 1/1] Broadcom devicetree fixes for 4.15 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=20171127200817.32647-1-f.fainelli@gmail.com \
--to=f.fainelli@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).