From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Borislav Petkov <bp@alien8.de>
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: Mon, 26 Jan 2026 10:41:21 -0600 [thread overview]
Message-ID: <3946f7ad-6ac8-4a5a-bfe5-92a5f6df5b31@kernel.org> (raw)
In-Reply-To: <20260126154037.GBaXeK9bxgPMdE2lFr@fat_crate.local>
On 1/26/2026 9:40 AM, Borislav Petkov wrote:
> On Mon, Jan 26, 2026 at 09:15:58AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
>> I think if slicing and dicing the string I would instead have us "match"
>> "AGESA!V9" instead and then spit it out like this:
>>
>> AGESA: StrixPI-FP8 1.0.0.1d
>>
>> Then if there's a v10 sentinel some day or something like that we would add
>> a new match then.
>
> Or, we can simply keep it simple and do:
>
> [ 0.840480] AGESA: AGESA!V9 StrixPI-FP8 1.0.0.1d
>
> A little redundancy won't hurt - having the version is much more important.
>
> Thx.
>
Well now you see why I was proposing the x86/amd: prefix in the first
place. It could be no slicing and dicing and with that prefix:
x86/amd: AGESA!V9 StrixPI-FP8 1.0.0.1d
next prev parent reply other threads:[~2026-01-26 16:41 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) [this message]
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
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=3946f7ad-6ac8-4a5a-bfe5-92a5f6df5b31@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
Powered by JetHome