From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 35406f0101abb63be458a7ae85334a7e03b71c31
Date: Fri, 24 Nov 2023 12:38:02 +0000 [thread overview]
Message-ID: <4ScDzJ5tsfz2xVv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3888 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 35406f0101abb63be458a7ae85334a7e03b71c31 (commit)
via 166b3cf2284a0480e7cdf86e005bb9b56ec137b6 (commit)
from 4bc2da437cc3900338c926fea0d9cb28d52aefb0 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 35406f0101abb63be458a7ae85334a7e03b71c31
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Fri Nov 24 12:37:24 2023 +0000
Core Update 182: Ship intel-microcode
The initial ramdisks are already rebuilt during the update at this
stage.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
commit 166b3cf2284a0480e7cdf86e005bb9b56ec137b6
Author: Adolf Belka <adolf.belka(a)ipfire.org>
Date: Fri Nov 24 12:44:03 2023 +0100
intel-microcode: Update to version 20231114
- 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>
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/x86_64/intel-microcode | 3 ---
.../{oldcore/121 => core/182}/filelists/x86_64/intel-microcode | 0
lfs/intel-microcode | 4 ++--
3 files changed, 2 insertions(+), 5 deletions(-)
copy config/rootfiles/{oldcore/121 => core/182}/filelists/x86_64/intel-microcode (100%)
Difference in files:
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/config/rootfiles/core/182/filelists/x86_64/intel-microcode b/config/rootfiles/core/182/filelists/x86_64/intel-microcode
new file mode 120000
index 000000000..d5ac074e2
--- /dev/null
+++ b/config/rootfiles/core/182/filelists/x86_64/intel-microcode
@@ -0,0 +1 @@
+../../../../common/x86_64/intel-microcode
\ No newline at end of file
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)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-11-24 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ScDzJ5tsfz2xVv@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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