From: Jean Delvare <jdelvare@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Mario Limonciello <superm1@kernel.org>,
Yazen Ghannam <yazen.ghannam@amd.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, 31 Mar 2026 19:59:03 +0200 [thread overview]
Message-ID: <20260331195903.633d493b@endymion> (raw)
In-Reply-To: <20260317191842.GFabmpEltxX2Akh1NF@fat_crate.local>
Hi Borislav,
On Tue, 17 Mar 2026 20:18:42 +0100, Borislav Petkov wrote:
> On Tue, Mar 17, 2026 at 01:28:02PM -0500, Mario Limonciello wrote:
> > 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?
>
> Sure, I can do that.
>
> @Jean, ack to the first 4 patches to go through tip?
I have reviewed the first 4 patches and they look good to me. You can
add:
Reviewed-by: Jean Delvare <jdelvare@suse.de>
to the patches which do not have it yet, and I am OK with them going
through tip.
Thanks Mario, Borislav and Yazen for all the work on this series!
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2026-03-31 17:59 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
2026-03-17 19:18 ` Borislav Petkov
2026-03-31 17:59 ` Jean Delvare [this message]
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=20260331195903.633d493b@endymion \
--to=jdelvare@suse.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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