From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v3 0/5] Parse SMBIOS additional entries
Date: Fri, 16 Jan 2026 09:08:10 -0600 [thread overview]
Message-ID: <8e0d404a-ed3d-4c24-b887-26445b057dca@kernel.org> (raw)
In-Reply-To: <20260116150318.GA402070@yaz-khff2.amd.com>
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.
prev parent reply other threads:[~2026-01-16 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 13:48 [PATCH v3 0/5] Parse SMBIOS additional entries Mario Limonciello (AMD)
2026-01-10 13:48 ` [PATCH v3 1/5] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2026-01-10 13:48 ` [PATCH v3 2/5] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2026-01-10 13:48 ` [PATCH v3 3/5] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2026-01-16 20:47 ` Yazen Ghannam
2026-01-10 13:48 ` [PATCH v3 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c Mario Limonciello (AMD)
2026-01-16 21:00 ` Yazen Ghannam
2026-01-10 13:48 ` [PATCH v3 5/5] firmware: dmi: Read additional information when decoding DMI table Mario Limonciello (AMD)
2026-01-16 21:30 ` Yazen Ghannam
2026-01-20 21:45 ` Yazen Ghannam
2026-01-20 21:55 ` Mario Limonciello
2026-01-20 22:05 ` Yazen Ghannam
2026-01-16 15:03 ` [PATCH v3 0/5] Parse SMBIOS additional entries Yazen Ghannam
2026-01-16 15:08 ` Mario Limonciello (AMD) (kernel.org) [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=8e0d404a-ed3d-4c24-b887-26445b057dca@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.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