From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Maxime Ripard <maxime@cerno.tech>,
Stefan Wahren <stefan.wahren@i2se.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
olof@lixom.net, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 1/1 RESEND] Broadcom devicetree fixes for 5.17
Date: Mon, 28 Feb 2022 08:55:37 -0800 [thread overview]
Message-ID: <20220228165537.1950863-1-f.fainelli@gmail.com> (raw)
The following changes since commit cfb92440ee71adcc2105b0890bb01ac3cddb8507:
Linux 5.17-rc5 (2022-02-20 13:07:20 -0800)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.17/devicetree-fixes
for you to fetch changes up to 515415d316168c6521d74ea8280287e28d7303e6:
ARM: boot: dts: bcm2711: Fix HVS register range (2022-02-23 11:03:29 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
5.17, please pull the following:
- Maxime fixes the HVS (display) register range for the BCM2711
(Raspberry Pi 4) SoC
----------------------------------------------------------------
Maxime Ripard (1):
ARM: boot: dts: bcm2711: Fix HVS register range
arch/arm/boot/dts/bcm2711.dtsi | 1 +
1 file changed, 1 insertion(+)
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Maxime Ripard <maxime@cerno.tech>,
Stefan Wahren <stefan.wahren@i2se.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
olof@lixom.net, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 1/1 RESEND] Broadcom devicetree fixes for 5.17
Date: Mon, 28 Feb 2022 08:55:37 -0800 [thread overview]
Message-ID: <20220228165537.1950863-1-f.fainelli@gmail.com> (raw)
The following changes since commit cfb92440ee71adcc2105b0890bb01ac3cddb8507:
Linux 5.17-rc5 (2022-02-20 13:07:20 -0800)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.17/devicetree-fixes
for you to fetch changes up to 515415d316168c6521d74ea8280287e28d7303e6:
ARM: boot: dts: bcm2711: Fix HVS register range (2022-02-23 11:03:29 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
5.17, please pull the following:
- Maxime fixes the HVS (display) register range for the BCM2711
(Raspberry Pi 4) SoC
----------------------------------------------------------------
Maxime Ripard (1):
ARM: boot: dts: bcm2711: Fix HVS register range
arch/arm/boot/dts/bcm2711.dtsi | 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:[~2022-02-28 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 16:55 Florian Fainelli [this message]
2022-02-28 16:55 ` [GIT PULL 1/1 RESEND] Broadcom devicetree fixes for 5.17 Florian Fainelli
2022-03-01 12:40 ` patchwork-bot+linux-soc
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=20220228165537.1950863-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=maxime@cerno.tech \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--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 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.