From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: "Stefan Wahren" <stefan.wahren@i2se.com>,
"Hamish Martin" <hamish.martin@alliedtelesis.co.nz>,
"Florian Fainelli" <f.fainelli@gmail.com>,
arnd@arndb.de, khilman@kernel.org,
"Vincent Stehlé" <vincent.stehle@laposte.net>,
bcm-kernel-feedback-list@broadcom.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/1] Broadcom devicetree fixes for 5.7 (part 2, v2)
Date: Sun, 24 May 2020 13:37:14 -0700 [thread overview]
Message-ID: <20200524203714.17035-1-f.fainelli@gmail.com> (raw)
The following changes since commit b9bbe6ed63b2b9f2c9ee5cbd0f2c946a2723f4ce:
Linux 5.7-rc6 (2020-05-17 16:48:37 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.7/devicetree-fixes-part2-v2
for you to fetch changes up to be0ec060b54f0481fb95d59086c1484a949c903c:
ARM: dts: bcm: HR2: Fix PPI interrupt types (2020-05-20 17:15:16 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
5.7, please pull the following:
- Vincent fixes the polarity of the ACT LED on the Raspberry Pi Zero W
board
- Hamish fixes the ARM PPI interrupts sensitivy for the Hurricane 2
SoCs
----------------------------------------------------------------
Hamish Martin (1):
ARM: dts: bcm: HR2: Fix PPI interrupt types
Vincent Stehlé (1):
ARM: dts: bcm2835-rpi-zero-w: Fix led polarity
arch/arm/boot/dts/bcm-hr2.dtsi | 6 +++---
arch/arm/boot/dts/bcm2835-rpi-zero-w.dts | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-05-24 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200524203714.17035-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hamish.martin@alliedtelesis.co.nz \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=vincent.stehle@laposte.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