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 6.20 #1
Date: Tue, 13 Jan 2026 14:46:02 +0100 [thread overview]
Message-ID: <4560446.MSiuQNM8U4@diego> (raw)
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.20-rockchip-dts32-1
for you to fetch changes up to e74470cf3101da79666f20186c9406192223e9a8:
ARM: dts: rockchip: Add vdec node for RK3288 (2025-12-15 12:21:05 +0100)
----------------------------------------------------------------
HEVC decoder node for RK3288.
----------------------------------------------------------------
Alex Bee (1):
ARM: dts: rockchip: Add vdec node for RK3288
arch/arm/boot/dts/rockchip/rk3288.dtsi | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
next reply other threads:[~2026-01-13 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 13:46 Heiko Stuebner [this message]
2026-01-22 15:42 ` [GIT PULL] Rockchip dts32 changes for 6.20 #1 Krzysztof Kozlowski
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=4560446.MSiuQNM8U4@diego \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox