From: Florian Fainelli <f.fainelli@gmail.com>
To: arm@kernel.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Matthias Lueschner <lueschem@gmail.com>,
arnd@arndb.de, khilman@kernel.org, Eric Anholt <eric@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/1] Broadcom devicetree fixes for 4.20
Date: Mon, 3 Dec 2018 12:47:21 -0800 [thread overview]
Message-ID: <20181203204721.4434-1-f.fainelli@gmail.com> (raw)
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.20/devicetree-fixes
for you to fetch changes up to e25b6783c7b1bb79103d4617336879423f86b05e:
ARM: dts: bcm2837: Fix polarity of wifi reset GPIOs (2018-12-03 11:51:26 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes,
please pull the following for 4.20:
- Stefan fixes the polariy of the Wi-Fi reset GPIOs signals which would
break on Raspberry Pi 3B and 3B+
----------------------------------------------------------------
Stefan Wahren (1):
ARM: dts: bcm2837: Fix polarity of wifi reset GPIOs
arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts | 2 +-
arch/arm/boot/dts/bcm2837-rpi-3-b.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2018-12-03 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 20:47 Florian Fainelli [this message]
2018-12-03 21:05 ` [GIT PULL 1/1] Broadcom devicetree fixes for 4.20 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=20181203204721.4434-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=eric@anholt.net \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lueschem@gmail.com \
--cc=olof@lixom.net \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).