From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip dts32 changes for 7.2 #1
Date: Tue, 26 May 2026 23:17:09 +0200 [thread overview]
Message-ID: <14415443.zAa99ISigo@phil> (raw)
Hi soc maintainers,
please find below Rockchip ARM32 DT changes for the merge-window for 7.2 .
Please pull.
Thanks
Heiko
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v7.2-rockchip-dts32
for you to fetch changes up to 98461edf564a35ee00a97a64f5463eaece586546:
ARM: dts: rockchip: Add #{address,size}-cells to Chromium-based /firmware (2026-05-05 19:26:18 +0200)
----------------------------------------------------------------
Cleanups for RK3288-based ChromeOS platform.
----------------------------------------------------------------
Brian Norris (1):
ARM: dts: rockchip: Add #{address,size}-cells to Chromium-based /firmware
Fabio Estevam (1):
ARM: dts: rockchip: Remove invalid properies from rk3288-veyron-analog-audio
arch/arm/boot/dts/rockchip/rk3288-veyron-analog-audio.dtsi | 2 --
arch/arm/boot/dts/rockchip/rk3288-veyron.dtsi | 5 +++++
2 files changed, 5 insertions(+), 2 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip dts32 changes for 7.2 #1
Date: Tue, 26 May 2026 23:17:09 +0200 [thread overview]
Message-ID: <14415443.zAa99ISigo@phil> (raw)
Hi soc maintainers,
please find below Rockchip ARM32 DT changes for the merge-window for 7.2 .
Please pull.
Thanks
Heiko
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v7.2-rockchip-dts32
for you to fetch changes up to 98461edf564a35ee00a97a64f5463eaece586546:
ARM: dts: rockchip: Add #{address,size}-cells to Chromium-based /firmware (2026-05-05 19:26:18 +0200)
----------------------------------------------------------------
Cleanups for RK3288-based ChromeOS platform.
----------------------------------------------------------------
Brian Norris (1):
ARM: dts: rockchip: Add #{address,size}-cells to Chromium-based /firmware
Fabio Estevam (1):
ARM: dts: rockchip: Remove invalid properies from rk3288-veyron-analog-audio
arch/arm/boot/dts/rockchip/rk3288-veyron-analog-audio.dtsi | 2 --
arch/arm/boot/dts/rockchip/rk3288-veyron.dtsi | 5 +++++
2 files changed, 5 insertions(+), 2 deletions(-)
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2026-05-26 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 21:17 Heiko Stuebner [this message]
2026-05-26 21:17 ` [GIT PULL] Rockchip dts32 changes for 7.2 #1 Heiko Stuebner
2026-06-02 11: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=14415443.zAa99ISigo@phil \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=soc@kernel.org \
/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.