From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
arnd@arndb.de, khilman@kernel.org,
Phil Elwell <phil@raspberrypi.org>,
bcm-kernel-feedback-list@broadcom.com,
Stefan Wahren <wahrenst@gmx.net>,
olof@lixom.net, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom devicetree fixes for 5.4
Date: Tue, 15 Oct 2019 10:23:55 -0700 [thread overview]
Message-ID: <20191015172356.9650-1-f.fainelli@gmail.com> (raw)
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.4/devicetree-fixes
for you to fetch changes up to 9786340acaa33b3722925125e2df358d14b8ee12:
ARM: dts: bcm2835-rpi-zero-w: Fix bus-width of sdhci (2019-10-15 10:18:32 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
5.4, please pull the following:
- Stefan fixes the MMC controller bus-width property for the Raspberry Pi
Zero Wireless which was incorrect after a prior refactoring
----------------------------------------------------------------
Stefan Wahren (1):
ARM: dts: bcm2835-rpi-zero-w: Fix bus-width of sdhci
arch/arm/boot/dts/bcm2835-rpi-zero-w.dts | 1 +
1 file changed, 1 insertion(+)
_______________________________________________
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-10-15 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 17:23 Florian Fainelli [this message]
2019-10-15 17:23 ` [GIT PULL 2/2] Broadcom devicetree-arm64 fixes for 5.4 Florian Fainelli
2019-10-18 19:02 ` [GIT PULL 1/2] Broadcom devicetree " Florian Fainelli
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=20191015172356.9650-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--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 \
--cc=phil@raspberrypi.org \
--cc=soc@kernel.org \
--cc=wahrenst@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.