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. 20220310 -> 20220411.
Date: Fri, 22 Apr 2022 07:35:32 +0200	[thread overview]
Message-ID: <20220422053532.741131-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220414093148.744989-1-christian.melki@t2data.com>

Thanks, applied as d1fb91928772f62399c2a4957dd7fef3e9113828.

Michael

[sent from post-receive hook]

On Fri, 22 Apr 2022 07:35:32 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Notable changes:
> New AMD CPU ucode. 2,5 years newer for family 17h.
> Various AMD gpu firmwares.
> Intel bluetooth chipsets and stray wifi stuff.
> 
> * Add comment about license data generation to
> ease maintainer understanding of existing ordering.
> * Fix whitespace mishap.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220414093148.744989-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 525ef6999b49..ef79a925dc7c 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	:= 20220310
> -LINUX_FIRMWARE_MD5	:= 77ce7e5531264d8726aeb3be3872f2f9
> +LINUX_FIRMWARE_VERSION	:= 20220411
> +LINUX_FIRMWARE_MD5	:= 1656a76666400bfb3c3f531cf5fc11d2
>  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))
> @@ -23,6 +23,8 @@ LINUX_FIRMWARE_SOURCE	:= $(SRCDIR)/$(LINUX_FIRMWARE).$(LINUX_FIRMWARE_SUFFIX)
>  LINUX_FIRMWARE_DIR	:= $(BUILDDIR)/$(LINUX_FIRMWARE)
>  LINUX_FIRMWARE_DEVPKG	:= NO
>  LINUX_FIRMWARE_LICENSE	:= proprietary
> +
> +# Order: find -type f \( -name "*LICENSE*" -o -name "*LICENCE*" \)
>  LINUX_FIRMWARE_LICENSE_FILES := \
>  	file://LICENCE.xc4000;md5=0ff51d2dc49fce04814c9155081092f0 \
>  	file://LICENCE.iwlwifi_firmware;md5=2ce6786e0fc11ac6e36b54bb9b799f1b \
> @@ -94,7 +96,7 @@ LINUX_FIRMWARE_LICENSE_FILES := \
>  	file://LICENCE.tda7706-firmware.txt;md5=835997cf5e3c131d0dddd695c7d9103e \
>  	file://LICENCE.cypress;md5=48cd9436c763bf873961f9ed7b5c147b \
>  	file://wfx/LICENCE.wf200;md5=4d1beff00d902c05c9c7e95a5d8eb52d \
> -	file://LICENSE.nxp_mc_firmware;md5=9dc97e4b279b3858cae8879ae2fe5dd7  \
> +	file://LICENSE.nxp_mc_firmware;md5=9dc97e4b279b3858cae8879ae2fe5dd7 \
>  	file://LICENCE.IntcSST2;md5=9e7d8bea77612d7cc7d9e9b54b623062 \
>  	file://LICENCE.ti-tspa;md5=d1a0eb27d0020752040190b9d51ad9be
>  

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2022-04-22  5:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  9:31 [ptxdist] [PATCH] " Christian Melki
2022-04-22  5:35 ` 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=20220422053532.741131-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