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 defconfig64 changes for 6.14 #1
Date: Sat, 11 Jan 2025 00:56:46 +0100 [thread overview]
Message-ID: <3095859.687JKscXgg@diego> (raw)
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.14-rockchip-defconfig64-1
for you to fetch changes up to 06835ccec2efb71d54a810265e8ef69b1011608e:
arm64: defconfig: Enable Rockchip extensions for Synopsys DW HDMI QP (2025-01-10 00:21:25 +0100)
----------------------------------------------------------------
Rockchip DRM extension for the DW-HDMI-QP controller and rfkill-gpio.
----------------------------------------------------------------
Cristian Ciocaltea (1):
arm64: defconfig: Enable Rockchip extensions for Synopsys DW HDMI QP
Nicolas Dufresne (1):
arm64: defconfig: Enable RFKILL GPIO
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
reply other threads:[~2025-01-11 0:00 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=3095859.687JKscXgg@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