From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] intel-microcode: Update to version 20240514
Date: Thu, 16 May 2024 13:13:03 +0100 [thread overview]
Message-ID: <F9E3C375-463F-4BB5-A00C-B794818012C6@ipfire.org> (raw)
In-Reply-To: <20240515153209.3410691-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 15 May 2024, at 16:32, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from version 20240312 to 20240514
> - Update of rootfile not required.
> - For the changelog details see the releasenote.md file in the source tarball.
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/intel-microcode | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/intel-microcode b/lfs/intel-microcode
> index 785b2303b..a1f7d6737 100644
> --- a/lfs/intel-microcode
> +++ b/lfs/intel-microcode
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 20240312
> +VER = 20240514
>
> THISAPP = Intel-Linux-Processor-Microcode-Data-Files-microcode-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -41,7 +41,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 43c771becef0f6dbfd41bf78a9a3cc8f6679a43ea48765d0e7f555c138dca6e3db42a4d33f743d8d51f38b0b6aa69322bba0c00ae9f1ff4c533b52166ee54747
> +$(DL_FILE)_BLAKE2 = 2a3a357ecf8d9f17fd20cd651386e5687fbbca8a3a323caf846e7c84d440241c3c99cadd00016642c8d11f297c1d2ab63c54ea062644839b74f84d66b04c703e
>
> install : $(TARGET)
>
> --
> 2.44.0
>
prev parent reply other threads:[~2024-05-16 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 15:32 Adolf Belka
2024-05-16 12:13 ` Michael Tremer [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=F9E3C375-463F-4BB5-A00C-B794818012C6@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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