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: <20260121143720.GDaXDkoAF1SLmiX0qb@fat_crate.local>
Date: Wed, 21 Jan 2026 15:37:20 +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 v4 5/6] x86/CPU/AMD: Prefix messages with x86/amd

On Wed, Jan 21, 2026 at 08:28:26AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
> Well so if I drop this patch, I still want to apply some sort of prefix to
> patch 6/6.  Because otherwise you end up with an AGESA string with no
> context of what that actually means or goes with.

Other useful strings don't have a prefix either:

[    0.000000] DMI: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PRO (MS-7B79), BIOS 1.70 01/23/2019

> Any other ideas of what to prefix that with?  Maybe:
> pr_info("AMD BIOS: %s\n")

"AGESA: ..."

AGESA is unique and AMD-specific.

-- 
Regards/Gruss,
    Boris.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ