Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry

Next message: David Carlier: "[PATCH v2] sched_ext/selftests: Fix bpf_link leak on assertion failure"
Previous message: Matthew Brost: "Re: [RFC PATCH 02/12] drm/dep: Add DRM dependency queue layer"
In reply to: Borislav Petkov: "Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry"
Next in thread: Borislav Petkov: "Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Mario Limonciello

Date: Tue Mar 17 2026 - 14:33:35 EST

On 3/17/26 13:24, Borislav Petkov wrote:

On Mon, Mar 16, 2026 at 09:33:04PM -0500, Mario Limonciello wrote:

But that can't actually happen. info->header.length is u8.

So we're never going to end up with that many entries such that it would
exhaust the check.

Ah ok, I didn't see that. That's good then. I guess we can start queueing the
next version you send with all the feedback incorporated.

Thx.

The only remaining feedback is commit message IIRC. Do you want to just massage that yourself while committing or do you want me to spin again and do it?