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. 20250211 -> 20250311
Date: Mon, 24 Mar 2025 08:45:47 +0100 [thread overview]
Message-ID: <20250324074547.2432133-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250312192331.1256881-1-christian.melki@t2data.com>
Thanks, applied as 9f18bcec67fa161aa4cc493bf40e3101f3951db0.
Michael
[sent from post-receive hook]
On Mon, 24 Mar 2025 08:45:47 +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=20250311
>
> * Added Intel VPU license (old name Versatile Processing Unit, now marketed as NPU).
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250312192331.1256881-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 c1a76fc09b71..2bee187dfeb7 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 := 20250211
> -LINUX_FIRMWARE_MD5 := 119c07da87e4a0806263b312fe86b8aa
> +LINUX_FIRMWARE_VERSION := 20250311
> +LINUX_FIRMWARE_MD5 := 83d8b0ca78b5da2f4c496e8f6fc5343a
> 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))
> @@ -93,6 +93,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
> file://LICENCE.rockchip;md5=5fd70190c5ed39734baceada8ecced26 \
> file://LICENSE.ixp4xx;md5=ddc5cd6cbc6745343926fe7ecc2cdeb2 \
> file://LICENCE.it913x;md5=1fbf727bfb6a949810c4dbfa7e6ce4f8 \
> + file://LICENSE.intel_vpu;md5=1e231b7287d5a5018740041c352eb58e \
> file://LICENSE.qcom_yamato;md5=d0de0eeccaf1843a850bf7a6777eec5c \
> file://LICENSE.qcom-2;md5=165287851294f2fb8ac8cbc5e24b02b0 \
> file://LICENCE.OLPC;md5=5b917f9d8c061991be4f6f5f108719cd \
prev parent reply other threads:[~2025-03-24 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 19:23 [ptxdist] [PATCH] " Christian Melki
2025-03-24 7:45 ` 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=20250324074547.2432133-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