From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 7a6bac40fd889b6852791bcde2c1a25ae3bdf65e
Date: Fri, 20 Nov 2020 20:04:58 +0000 [thread overview]
Message-ID: <4Cd6wB4rDZz2xjy@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1743 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 7a6bac40fd889b6852791bcde2c1a25ae3bdf65e (commit)
from 82973fae144d199c10332a174848db6eaddc1355 (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 7a6bac40fd889b6852791bcde2c1a25ae3bdf65e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Nov 20 20:04:13 2020 +0000
core153: Remove reloading microcode
This requires that we can load the "microcode" module, but
since the kernel was replaced in this release, we can't load
it any more.
Fixes: #12537
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/153/update.sh | 6 ------
1 file changed, 6 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/153/update.sh b/config/rootfiles/core/153/update.sh
index 4712a0c90..af85c1794 100644
--- a/config/rootfiles/core/153/update.sh
+++ b/config/rootfiles/core/153/update.sh
@@ -144,11 +144,5 @@ fi
sync
-# Reload microcode
-modprobe microcode
-if [ -w "/sys/devices/system/cpu/microcode/reload" ]; then
- echo 1 > /sys/devices/system/cpu/microcode/reload
-fi
-
# Don't report the exitcode last command
exit 0
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-11-20 20:04 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=4Cd6wB4rDZz2xjy@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