From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
soc@kernel.org, arnd@arndb.de, olof@lixom.net
Cc: "Stefan Wahren" <stefan.wahren@i2se.com>,
khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
"Vincent Stehlé" <vincent.stehle@laposte.net>
Subject: Re: [GIT PULL 1/1] Broadcom devicetree fixes for 5.7 (part 2)
Date: Wed, 20 May 2020 17:12:36 -0700 [thread overview]
Message-ID: <a6adb8e0-fb59-d085-42c6-e5ef890015b1@gmail.com> (raw)
In-Reply-To: <20200424224915.3541-1-f.fainelli@gmail.com>
Hi Arnd, Olof,
On 4/24/2020 3:49 PM, Florian Fainelli wrote:
> The following changes since commit 90444b958461a5f8fc299ece0fe17eab15cba1e1:
>
> ARM: dts: bcm283x: Disable dsi0 node (2020-04-16 13:58:02 -0700)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.7/devicetree-fixes-part2
>
> for you to fetch changes up to 2c972731a3d74a336519fb158fbe863caad5c421:
>
> ARM: dts: bcm2835-rpi-zero-w: Fix led polarity (2020-04-24 12:50:37 -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
>
> ----------------------------------------------------------------
> Vincent Stehlé (1):
> ARM: dts: bcm2835-rpi-zero-w: Fix led polarity
If you have not pulled this already (I could not find it in
linux-next/master or Linus' master), there is another one coming with
another fix.
Thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-05-21 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 22:49 [GIT PULL 1/1] Broadcom devicetree fixes for 5.7 (part 2) Florian Fainelli
2020-05-21 0:12 ` Florian Fainelli [this message]
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=a6adb8e0-fb59-d085-42c6-e5ef890015b1@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=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;
as well as URLs for NNTP newsgroup(s).