From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] intel-microcode: Update to version 20240531
Date: Mon, 03 Jun 2024 14:54:49 +0100 [thread overview]
Message-ID: <5BFA6B67-57AB-4A25-B370-160927883F31@ipfire.org> (raw)
In-Reply-To: <20240603121152.3408340-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
Thank you. That was very quick!
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 3 Jun 2024, at 13:11, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from version 20240514 to 20240531
> - Update of rootfile not required
> - Changelog
> 20240531
> Update for functional issues. Refer to
> https://cdrdv2.intel.com/v1/dl/getContent/336562
>
> 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 a1f7d6737..8cf0af29c 100644
> --- a/lfs/intel-microcode
> +++ b/lfs/intel-microcode
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 20240514
> +VER = 20240531
>
> 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 = 2a3a357ecf8d9f17fd20cd651386e5687fbbca8a3a323caf846e7c84d440241c3c99cadd00016642c8d11f297c1d2ab63c54ea062644839b74f84d66b04c703e
> +$(DL_FILE)_BLAKE2 = 6a2c5ee6b6f3543b28f3753b30812e360bad50776b4f81e32a832e2169f38c11f8d5108ce0a81ddcdf1ecf7557baf1fd62c053a365f39a33ded5fd5018580b1f
>
> install : $(TARGET)
>
> --
> 2.45.1
>
prev parent reply other threads:[~2024-06-03 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 12:11 Adolf Belka
2024-06-03 13:54 ` 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=5BFA6B67-57AB-4A25-B370-160927883F31@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