mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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. 20221109 -> 20221214
Date: Tue,  3 Jan 2023 12:08:28 +0100	[thread overview]
Message-ID: <20230103110828.2228711-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221215091402.2188099-1-christian.melki@t2data.com>

Thanks, applied as f310b0419ef86800220e2ff86eeaf2d435cdd282.

Michael

[sent from post-receive hook]

On Tue, 03 Jan 2023 12:08:28 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> A slew of baseline AMDGPU firmware updates.
> Otherwise mostly the usual radio firmwares.
> 
> * Add nxp license. Added by the NXP SR150 UWB hw.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20221215091402.2188099-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 29882aaf4583..1a1cdaa16f71 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	:= 20221109
> -LINUX_FIRMWARE_MD5	:= 6c9f675c49d36eae1012c5d23370817f
> +LINUX_FIRMWARE_VERSION	:= 20221214
> +LINUX_FIRMWARE_MD5	:= 93ba47547b9c2e538d11de95405939b2
>  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))
> @@ -63,6 +63,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
>  	file://LICENCE.ti-keystone;md5=3a86335d32864b0bef996bee26cc0f2c \
>  	file://LICENSE.amd-sev;md5=e750538791a8be0b7249c579edefb035 \
>  	file://LICENSE.amdgpu;md5=44c1166d052226cb2d6c8d7400090203 \
> +	file://LICENSE.nxp;md5=cca321ca1524d6a1e4fed87486cd82dc \
>  	file://LICENCE.agere;md5=af0133de6b4a9b2522defd5f188afd31 \
>  	file://LICENCE.siano;md5=4556c1bf830067f12ca151ad953ec2a5 \
>  	file://LICENCE.broadcom_bcm43xx;md5=3160c14df7228891b868060e1951dfbc \



      reply	other threads:[~2023-01-03 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  9:14 [ptxdist] [PATCH] " Christian Melki
2023-01-03 11:08 ` 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=20230103110828.2228711-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