From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] linux-firmware: Version bump 20251125 -> 20260110
Date: Sun, 11 Jan 2026 16:45:48 +0100 [thread overview]
Message-ID: <20260111154548.2737345-1-christian.melki@t2data.com> (raw)
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?h=20260110
* AMD u-code license had copyright year update.
* Added Renesas R-Car license (rcar_gen4_pcie)
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/linux-firmware.make | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/rules/linux-firmware.make b/rules/linux-firmware.make
index 6102aa8b7..4421c31a8 100644
--- a/rules/linux-firmware.make
+++ b/rules/linux-firmware.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LINUX_FIRMWARE) += linux-firmware
#
# Paths and names
#
-LINUX_FIRMWARE_VERSION := 20251125
-LINUX_FIRMWARE_MD5 := 7fdfe0f4768bed8ca9035e98815fc502
+LINUX_FIRMWARE_VERSION := 20260110
+LINUX_FIRMWARE_MD5 := c353e926f90e0c123eef24b447c953e0
LINUX_FIRMWARE := linux-firmware-$(LINUX_FIRMWARE_VERSION)
LINUX_FIRMWARE_SUFFIX := tar.gz
LINUX_FIRMWARE_URL := $(call ptx/mirror, KERNEL, kernel/firmware/$(LINUX_FIRMWARE).$(LINUX_FIRMWARE_SUFFIX))
@@ -33,7 +33,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
file://LICENCE.linaro;md5=936d91e71cf9cd30e733db4bf11661cc \
file://LICENCE.adsp_sst;md5=615c45b91a5a4a9fe046d6ab9a2df728 \
file://LICENCE.cadence;md5=009f46816f6956cfb75ede13d3e1cee0 \
- file://LICENSE.amd-ucode;md5=6ca90c57f7b248de1e25c7f68ffc4698 \
+ file://LICENSE.amd-ucode;md5=450f217aadc787514165e9568652d700 \
file://LICENSE.aeonsemi;md5=521c00bae0077c90d6ffb9ccf66905ae \
file://LICENSE.atmel;md5=aa74ac0c60595dee4d4e239107ea77a3 \
file://LICENCE.fw_sst_0f28;md5=6353931c988ad52818ae733ac61cd293 \
@@ -48,6 +48,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
file://LICENSE.tlg2300;md5=4b23ec9ced919a0bf2f7c56dac31b2b7 \
file://LICENSE.ice_enhanced;md5=f305cfc31b64f95f774f9edd9df0224d \
file://LICENCE.lenovo;md5=7f25420b5c27211f7bf33bebb3042ce4 \
+ file://LICENCE.r8a779g_pcie_phy;md5=0b20e76a9a004b83c4a1c87e2153bbad \
file://LICENSE.qcom;md5=164e3362a538eb11d3ac51e8e134294b \
file://LICENCE.alacritech;md5=75dabc07cc2fb59d929baa6bd6aae48a \
file://LICENCE.ibt_firmware;md5=fdbee1ddfe0fb7ab0b2fcd6b454a366b \
--
2.43.0
reply other threads:[~2026-01-11 15:46 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=20260111154548.2737345-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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