From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] linux-firmware: Version bump. 20251011 -> 20251111
Date: Thu, 4 Dec 2025 14:14:43 +0100 [thread overview]
Message-ID: <20251204131443.2196474-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251112193759.1659500-1-christian.melki@t2data.com>
Thanks, applied as e1a9793882c42aa5697bb0db64e2fd1ec50e0c81.
Michael
[sent from post-receive hook]
On Thu, 04 Dec 2025 14:14:43 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> The usual suspects.
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?h=20251111
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20251112193759.1659500-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/linux-firmware.make b/rules/linux-firmware.make
> index 19e7b871b9f9..7708aa0b3085 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 := 20251011
> -LINUX_FIRMWARE_MD5 := 8e75d8a5e8692a389a68587c46fa908b
> +LINUX_FIRMWARE_VERSION := 20251111
> +LINUX_FIRMWARE_MD5 := dcb1262208088f77dbead342eaf226da
> 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))
prev parent reply other threads:[~2025-12-04 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 19:37 [ptxdist] [PATCH] " Christian Melki
2025-12-04 13:14 ` Michael Olbrich [this message]
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=20251204131443.2196474-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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