All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	arnd@arndb.de, khilman@kernel.org,
	Fredrik Yhlen <fredrik.yhlen@endian.se>,
	bcm-kernel-feedback-list@broadcom.com,
	Stefan Wahren <wahrenst@gmx.net>,
	olof@lixom.net, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL part 2] Broadcom devicetree fixes for 5.4
Date: Mon, 21 Oct 2019 12:43:02 -0700	[thread overview]
Message-ID: <20191021194302.21024-1-f.fainelli@gmail.com> (raw)

The following changes since commit 9786340acaa33b3722925125e2df358d14b8ee12:

  ARM: dts: bcm2835-rpi-zero-w: Fix bus-width of sdhci (2019-10-15 10:18:32 -0700)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.4/devicetree-fixes-part2

for you to fetch changes up to 626c45d223e22090511acbfb481e0ece1de1356d:

  ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue (2019-10-18 11:59:39 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoC Device Tree fixes for
5.4, please pull the following:

- Stefan removes the activity LED node from the CM3 DTS since there is
  no driver for that LED yet and leds-gpio cannot drive it either

----------------------------------------------------------------
Stefan Wahren (1):
      ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue

 arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi | 8 ++++++++
 1 file changed, 8 insertions(+)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2019-10-21 19:43 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=20191021194302.21024-1-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=fredrik.yhlen@endian.se \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --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.