public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [intel/Intel-Linux-Processor-Microcode-Data-Files] Release microcode-20241029 - microcode-20241029 Release
Date: Wed, 30 Oct 2024 14:43:11 +0100	[thread overview]
Message-ID: <4314e71c-93c9-4d06-9bcb-86c1292b3772@ipfire.org> (raw)
In-Reply-To: <09C459B1-7EAB-484E-9B12-AC6241875927@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2566 bytes --]

Hi Michael,

Patch for update has been submitted.

I have been starting some work on setting up a cloudflare DDNS provider 
entry for the DDNS system triggered by the IPFire bugzilla bug. 
Therefore I had a source file in my local repo ddns-016.tar.xz and when 
I ran my make.sh uploadsrc I not only uploaded the intel microcode 
source tarball but also my evaluation ddns-016.tar.xz tarball.

Can you please delete this tarball from the source directory on the 
IPFire server.

Any final version will be different to what is in that source tarball, 
it is only a test version for me to evaluate some things. It was not 
intended to get uploaded but I forgot I had it in my cache directory 
from a couple of days earlier.

Regards,

Adolf.


On 30/10/2024 10:54, Michael Tremer wrote:
> Thank you!
> 
>> On 30 Oct 2024, at 09:50, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> I will pick this up.
>>
>> Regards,
>>
>> Adolf.
>>
>>
>> On 30/10/2024 10:28, Michael Tremer wrote:
>>> Is anyone up for grabbing this one?
>>>
>>>> Begin forwarded message:
>>>>
>>>> From: MCU Administrator <notifications(a)github.com>
>>>> Subject: [intel/Intel-Linux-Processor-Microcode-Data-Files] Release microcode-20241029 - microcode-20241029 Release
>>>> Date: 29 October 2024 at 23:50:48 GMT
>>>> 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-20241029 Release
>>>> Repository: intel/Intel-Linux-Processor-Microcode-Data-Files · Tag: microcode-20241029 · Commit: 129f82f · Released by: mcu-administrator
>>>> Release Notes microcode-20241029 Purpose
>>>>      • Update for functional issues. Refer to 14th/13th Generation Intel® Core™ Processor Specification Update for details.
>>>> 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 RPL-E/HX/S B0 06-b7-01/32 00000129 0000012b Core Gen13/Gen14 —
>>>> This release has 2 assets:
>>>>      • Source code (zip)
>>>>      • Source code (tar.gz)
>>>> Visit the release page to download them.
>>>> —
>>>> You are receiving this because you are watching this repository.
>>>> View it on GitHub or unsubscribe from all notifications for this repository.
>>>
>>
>> -- 
>> Sent from my laptop
> 

-- 
Sent from my laptop


      reply	other threads:[~2024-10-30 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0b84234d-0ea4-4ac7-835e-5d938503e3b5@ipfire.org>
2024-10-30  9:54 ` Michael Tremer
2024-10-30 13:43   ` Adolf Belka [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=4314e71c-93c9-4d06-9bcb-86c1292b3772@ipfire.org \
    --to=adolf.belka@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