[an error occurred while processing this directive]

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

[an error occurred while processing this directive]

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

Message-ID: <20260126165412.GCaXecNPIySsrmirfC@fat_crate.local>
Date: Mon, 26 Jan 2026 17:54:12 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Mario Limonciello (AMD) (kernel.org)" <superm1@...nel.org>
Cc: Yazen Ghannam <yazen.ghannam@....com>, Jean Delvare <jdelvare@...e.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI
 additional information entry

On Mon, Jan 26, 2026 at 10:41:21AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
> 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

So the prefix tells so that it is somewhere from x86/.../amd.

The "AGESA:" prefix tells you it is AGESA.

I don't see how the "x86/amd" prefix works here...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette