linux-kernel - Re: [PATCH v3] x86/CPU/AMD: Prefix messages with x86/amd

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: <20260110135349.GBaWJZ7RayAKdIamdY@fat_crate.local>
Date: Sat, 10 Jan 2026 14:53:49 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Mario Limonciello (AMD) (kernel.org)" <superm1@...nel.org>
Cc: mario.limonciello@....com, tglx@...utronix.de, mingo@...hat.com,
	dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Yazen Ghannam <yazen.ghannam@....com>
Subject: Re: [PATCH v3] x86/CPU/AMD: Prefix messages with x86/amd

On Sat, Jan 10, 2026 at 07:39:35AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
> Well originally the reason was that another message was being added in a
> series.  But the review of the series was deciding not to do it that way.
> But this way any other future messages pick up the prefix already.
> 
> It's a trivial patch, but if you want to wait until another message comes
> around again we can hold off.

I'm actually wondering whether there's any specific reason to denote that the
messages come from this particular compilation unit...?

-- 
Regards/Gruss,
    Boris.

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