From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] intel-microcode: Update to version 20231114
Date: Fri, 24 Nov 2023 11:44:46 +0000 [thread overview]
Message-ID: <1AB026FB-0341-49A6-930E-F538B3AD8E9C@ipfire.org> (raw)
In-Reply-To: <20231124114404.3382731-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
Thanks again!
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 24 Nov 2023, at 11:44, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from version 20230808 to 20231114
> - Update of rootfile
> - Changelog details can be found in the releasenote.md file from the source tarball
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/x86_64/intel-microcode | 3 ---
> lfs/intel-microcode | 4 ++--
> 2 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/config/rootfiles/common/x86_64/intel-microcode b/config/rootfiles/common/x86_64/intel-microcode
> index 3241092f3..7f9632973 100644
> --- a/config/rootfiles/common/x86_64/intel-microcode
> +++ b/config/rootfiles/common/x86_64/intel-microcode
> @@ -119,11 +119,8 @@ lib/firmware/intel-ucode/06-a6-01
> lib/firmware/intel-ucode/06-a7-01
> lib/firmware/intel-ucode/06-b7-01
> lib/firmware/intel-ucode/06-ba-02
> -lib/firmware/intel-ucode/06-ba-02_DUPLICATE
> lib/firmware/intel-ucode/06-ba-03
> -lib/firmware/intel-ucode/06-ba-03_DUPLICATE
> lib/firmware/intel-ucode/06-be-00
> -lib/firmware/intel-ucode/06-be-00_DUPLICATE
> lib/firmware/intel-ucode/06-bf-02
> lib/firmware/intel-ucode/06-bf-05
> lib/firmware/intel-ucode/0f-00-07
> diff --git a/lfs/intel-microcode b/lfs/intel-microcode
> index 4bb322ac5..5e262dda3 100644
> --- a/lfs/intel-microcode
> +++ b/lfs/intel-microcode
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 20230808
> +VER = 20231114
>
> 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 = 400ba9b91a7048c780377d49ff6cb00458c60a9d53c2e5cef1eb99170ca8f0cad66336841d14869bd42d182f7d8df27a2fa9cb982b0df0c5fc9f62325b6acb69
> +$(DL_FILE)_BLAKE2 = e6084c92e9c3cc627af25a7f2f7fb26230b6ed117ddc197d19991df2816334132af92925f23af829bad005c32d0bd3afc362055ef223a599799d846216cf7612
>
> install : $(TARGET)
>
> --
> 2.42.1
>
prev parent reply other threads:[~2023-11-24 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 11:44 Adolf Belka
2023-11-24 11:44 ` 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=1AB026FB-0341-49A6-930E-F538B3AD8E9C@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