From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/ucode: Add extra rows to the entrysign model table
Date: Mon, 10 Nov 2025 10:27:31 +0100 [thread overview]
Message-ID: <10d0601b-14d8-4a7e-b8e5-dc4bc1d19aa6@gmail.com> (raw)
In-Reply-To: <36cdbd68-3285-4c96-b25e-9a0474a9a2ab@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On 11/7/25 3:34 PM, Andrew Cooper wrote:
> On 07/11/2025 2:30 pm, Jan Beulich wrote:
>> On 07.11.2025 14:47, Andrew Cooper wrote:
>>> Link:https://git.kernel.org/tip/d23550efc6800841b4d1639784afaebdea946ae0
>>> Fixes: ff8228ab4658 ("x86/ucode: Relax digest check when Entrysign is fixed in firmware")
>>> Signed-off-by: Andrew Cooper<andrew.cooper3@citrix.com>
>> Acked-by: Jan Beulich<jbeulich@suse.com>
>>
>> Pretty likely wants to go into 4.21? Cc-ing Oleksii, for him to judge.
> Yes, and backporting, but I've got more ucode bugfixes I'm working on.
>
> One in particular was always broken, but exasperated by one of my recent
> changes, but I'm not sure if the result is going to be comfortable for
> 4.21 at this juncture.
I think it’s not a good idea to skip the SHA check, so it makes sense to
accept this patch:
Release-Acked-By: Oleksii Kurochko<oleksii.kurochko@gmail.com>
Thanks.
~ Oleksii
[-- Attachment #2: Type: text/html, Size: 1929 bytes --]
prev parent reply other threads:[~2025-11-10 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 13:47 [PATCH] x86/ucode: Add extra rows to the entrysign model table Andrew Cooper
2025-11-07 14:30 ` Jan Beulich
2025-11-07 14:34 ` Andrew Cooper
2025-11-10 9:27 ` Oleksii Kurochko [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=10d0601b-14d8-4a7e-b8e5-dc4bc1d19aa6@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).