From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>, Mario Limonciello <superm1@kernel.org>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>,
Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry
Date: Tue, 17 Mar 2026 13:28:02 -0500 [thread overview]
Message-ID: <7e31a065-66e3-4458-91c5-c9f03a366a41@amd.com> (raw)
In-Reply-To: <20260317182445.GEabmcbT3micfnPkhk@fat_crate.local>
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?
next prev parent reply other threads:[~2026-03-17 18:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 21:30 [PATCH v5 0/5] Print AGESA version at bootup Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 1/5] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 2/5] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 3/5] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry Mario Limonciello (AMD)
2026-01-26 13:07 ` Borislav Petkov
2026-01-26 15:15 ` Mario Limonciello (AMD) (kernel.org)
2026-01-26 15:40 ` Borislav Petkov
2026-01-26 16:41 ` Mario Limonciello (AMD) (kernel.org)
2026-01-26 16:54 ` Borislav Petkov
2026-01-28 14:39 ` Yazen Ghannam
2026-01-28 15:27 ` Mario Limonciello
2026-03-15 13:14 ` Borislav Petkov
2026-03-15 15:14 ` Mario Limonciello
2026-03-15 20:56 ` Borislav Petkov
2026-03-17 2:33 ` Mario Limonciello
2026-03-17 18:24 ` Borislav Petkov
2026-03-17 18:28 ` Mario Limonciello [this message]
2026-03-17 19:18 ` Borislav Petkov
2026-03-31 17:59 ` Jean Delvare
2026-03-31 18:09 ` Borislav Petkov
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=7e31a065-66e3-4458-91c5-c9f03a366a41@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=superm1@kernel.org \
--cc=yazen.ghannam@amd.com \
/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
Powered by JetHome