linux-kernel - Re: [PATCH v3 0/5] Parse SMBIOS additional entries

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8e0d404a-ed3d-4c24-b887-26445b057dca@kernel.org>
Date: Fri, 16 Jan 2026 09:08:10 -0600
From: "Mario Limonciello (AMD) (kernel.org)" <superm1@...nel.org>
To: Yazen Ghannam <yazen.ghannam@....com>
Cc: Jean Delvare <jdelvare@...e.com>, linux-kernel@...r.kernel.org,
 Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH v3 0/5] Parse SMBIOS additional entries



On 1/16/2026 9:03 AM, Yazen Ghannam wrote:
> On Sat, Jan 10, 2026 at 07:48:29AM -0600, Mario Limonciello (AMD) wrote:
>> The SMBIOS additional entries on AMD Zen4+ systems running an AGESA
>> based BIOS contain information about the AGESA version which can be
>> useful for matching the software stack when debugging an issue.
>>
>> Add support for parsing this from SMBIOS tables and output it into
>> the logs at bootup.  Additionally export the information to debugfs
>> in case users are interested in any other strings.
>>
>> v3:
>>   * Drop / merge patches from feedback
>>   * Don't save additional strings, only show AGESA string if found
>>
>> Mario Limonciello (1):
>>    firmware: dmi: Add pr_fmt() for dmi_scan.c
>>
>> Mario Limonciello (AMD) (4):
>>    firmware: dmi: Correct an indexing error in dmi.h
>>    firmware: dmi: Adjust dmi_decode() to use enums
>>    firmware: dmi: Add missing DMI entry types
>>    firmware: dmi: Read additional information when decoding DMI table
>>
> 
> One patch is authored with a different email. Is this intentional?
> 
> Not a problem, but wanted to ask just in case.
> 

It was an oversight because I worked on two different machines and 
forgot I had git configured differently when I made the commits.

If there are other changes needed for the series I'll fix it in next 
version, otherwise leaving it as is is totally fine for me.