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. 20221012 -> 20221109
Date: Tue, 22 Nov 2022 14:20:18 +0100 [thread overview]
Message-ID: <20221122132018.3159586-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221118195141.1486895-1-christian.melki@t2data.com>
Thanks, applied as 6af74c3d4f710310f21ab2eeed0de35a30eb03d5.
Michael
[sent from post-receive hook]
On Tue, 22 Nov 2022 14:20:18 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Usual churn of GPU and radio firmware updates.
> No new license files this time around.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20221118195141.1486895-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 0a0630ed7c69..29882aaf4583 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 := 20221012
> -LINUX_FIRMWARE_MD5 := 50fa95d6dc86758089df2981d704f36e
> +LINUX_FIRMWARE_VERSION := 20221109
> +LINUX_FIRMWARE_MD5 := 6c9f675c49d36eae1012c5d23370817f
> 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:[~2022-11-22 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 19:51 [ptxdist] [PATCH] " Christian Melki
2022-11-22 13:20 ` 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=20221122132018.3159586-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