From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [intel/Intel-Linux-Processor-Microcode-Data-Files] Release microcode-20240531 - microcode-20240531 Release
Date: Mon, 03 Jun 2024 10:51:29 +0100 [thread overview]
Message-ID: <C6297D6F-1D28-4E28-AEE0-7E1A0526D71A@ipfire.org> (raw)
In-Reply-To: <9254d48b-67b1-47d0-9b26-822668433b1a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2823 bytes --]
Thank you!
> On 3 Jun 2024, at 10:39, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> I will pick it up.
>
> Regards,
>
> Adolf.
>
>
> On 03/06/2024 11:30, Michael Tremer wrote:
>> Is anyone free to grab this one? Doesn’t sound too urgent to me, but we should have it updated of course.
>>
>> -Michael
>>
>>> Begin forwarded message:
>>>
>>> *From: *NayeliRico <notifications(a)github.com>
>>> *Subject: **[intel/Intel-Linux-Processor-Microcode-Data-Files] Release microcode-20240531 - microcode-20240531 Release*
>>> *Date: *1 June 2024 at 01:44:55 BST
>>> *To: *intel/Intel-Linux-Processor-Microcode-Data-Files <Intel-Linux-Processor-Microcode-Data-Files(a)noreply.github.com>
>>> *Cc: *Subscribed <subscribed(a)noreply.github.com>
>>> *Reply-To: *intel/Intel-Linux-Processor-Microcode-Data-Files <noreply(a)github.com>
>>>
>>>
>>> microcode-20240531 Release <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240531>
>>>
>>> Repository: intel/Intel-Linux-Processor-Microcode-Data-Files <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files> · Tag: microcode-20240531 <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/tree/microcode-20240531> · Commit: 5278dfc <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/commit/5278dfcf98e89098326b3eb8a85d07120a8730f8> · Released by: NayeliRico <https://github.com/NayeliRico>
>>>
>>>
>>> Release Notes
>>>
>>>
>>> microcode-20240531 <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240531>
>>>
>>>
>>> Purpose
>>>
>>> * Update for functional issues. Refer to Intel® Pentium® Silver and Intel® Celeron® Processor Specification Update <https://cdrdv2.intel.com/v1/dl/getContent/336562>
>>>
>>>
>>> New Platforms
>>>
>>> Processor Stepping F-M-S/PI Old Ver New Ver Products
>>>
>>>
>>> Updated Platforms
>>>
>>> Processor Stepping F-M-S/PI Old Ver New Ver Products
>>> GLK B0 06-7a-01/01 00000040 00000042 Pentium Silver N/J5xxx, Celeron N/J4xxx
>>>
>>> —
>>>
>>> This release has 2 assets:
>>>
>>> * Source code (zip)
>>> * Source code (tar.gz)
>>>
>>> Visit the release page <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240531> to download them.
>>>
>>> —
>>> You are receiving this because you are watching this repository.
>>> View it on GitHub <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240531> or unsubscribe <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/unsubscribe_via_email/ABQGVEVMUOXD6FYMYO55XLTZFEKQPANCNFSM4CS7UPPA> from all notifications for this repository.
>>>
>>
prev parent reply other threads:[~2024-06-03 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F16DFF4E-26B3-4CA5-9F09-14C4B2C3F6F5@ipfire.org>
2024-06-03 9:39 ` Fwd: " Adolf Belka
2024-06-03 9:51 ` 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=C6297D6F-1D28-4E28-AEE0-7E1A0526D71A@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