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. 20220411 -> 20220509
Date: Wed, 25 May 2022 11:45:05 +0200	[thread overview]
Message-ID: <20220525094505.2844867-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220510133929.3728267-1-christian.melki@t2data.com>

Thanks, applied as 4aa96e7abdd8cd6aa19bcd4c9874a73bf1416246.

Michael

[sent from post-receive hook]

On Wed, 25 May 2022 11:45:05 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Usual churn of firmware updates.
> Mostly wifi and gpu firmwares.
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?h=20220509
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220510133929.3728267-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 ef79a925dc7c..1c9082c8b132 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	:= 20220411
> -LINUX_FIRMWARE_MD5	:= 1656a76666400bfb3c3f531cf5fc11d2
> +LINUX_FIRMWARE_VERSION	:= 20220509
> +LINUX_FIRMWARE_MD5	:= ebf38affb619bc02dc64ebcba61a1ab9
>  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))



      reply	other threads:[~2022-05-25  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 13:39 [ptxdist] [PATCH] " Christian Melki
2022-05-25  9: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=20220525094505.2844867-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