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. 20220913 -> 20221012
Date: Fri, 28 Oct 2022 16:44:31 +0200 [thread overview]
Message-ID: <20221028144431.2271110-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221020131725.2594010-1-christian.melki@t2data.com>
Thanks, applied as 46956ae204a14b564da9d373c418ed47a544f6c4.
Michael
[sent from post-receive hook]
On Fri, 28 Oct 2022 16:44:31 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?h=20221012
> Usual churn of updates. GPUs, BT, Wifi.
>
> * Amd-ucode license file changed. New copyright year.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20221020131725.2594010-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 287bfd63e04e..0a0630ed7c69 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 := 20220913
> -LINUX_FIRMWARE_MD5 := 1ea1f09e040b8c86d4bc4a4e41acffc5
> +LINUX_FIRMWARE_VERSION := 20221012
> +LINUX_FIRMWARE_MD5 := 50fa95d6dc86758089df2981d704f36e
> 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))
> @@ -31,7 +31,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
> file://LICENSE.dib0700;md5=f7411825c8a555a1a3e5eab9ca773431 \
> file://LICENCE.adsp_sst;md5=615c45b91a5a4a9fe046d6ab9a2df728 \
> file://LICENCE.cadence;md5=009f46816f6956cfb75ede13d3e1cee0 \
> - file://LICENSE.amd-ucode;md5=3c5399dc9148d7f0e1f41e34b69cf14f \
> + file://LICENSE.amd-ucode;md5=6ca90c57f7b248de1e25c7f68ffc4698 \
> file://LICENSE.atmel;md5=aa74ac0c60595dee4d4e239107ea77a3 \
> file://LICENCE.fw_sst_0f28;md5=6353931c988ad52818ae733ac61cd293 \
> file://LICENSE.amphion_vpu;md5=2bcdc00527b2d0542bd92b52aaec2b60 \
prev parent reply other threads:[~2022-10-28 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 13:17 [ptxdist] [PATCH] " Christian Melki
2022-10-28 14:44 ` 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=20221028144431.2271110-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