From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] intel-microcode: update to 20200616
Date: Fri, 17 Jul 2020 11:02:56 +0100 [thread overview]
Message-ID: <F9BA466D-48BF-4791-AD6F-9FDC74CF563D@ipfire.org> (raw)
In-Reply-To: <19c08d56-4764-7cf8-e7bb-d38de5c2f4e9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
Yay \o/!
> On 15 Jul 2020, at 18:01, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Ice Lake Intel CPUs have been found of being vulnerable to MDS, thus
> requiring new microcodes for them. <sarcasm>Yay!</sarcasm> Please refer to
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20200616
> for further information.
>
> Signed-off-by: Peter Müller <peter.mueller(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 494062784..025a789a5 100644
> --- a/lfs/intel-microcode
> +++ b/lfs/intel-microcode
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 20200609
> +VER = 20200616
>
> 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)_MD5 = a03e827c5c43be594f7f34d75b1706f9
> +$(DL_FILE)_MD5 = b5e2f0cc9db2ed3d2760a5a859a0a387
>
> install : $(TARGET)
>
> --
> 2.26.2
prev parent reply other threads:[~2020-07-17 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 17:01 Peter Müller
2020-07-17 10:02 ` 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=F9BA466D-48BF-4791-AD6F-9FDC74CF563D@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