linux-kernel - Re: [PATCH v5 05/20] x86/mce: Cleanup bank processing on init

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] [day] [month] [year] [list]

Message-ID: <20250826143320.GAaK3FsOE2AjADWceY@fat_crate.local>
Date: Tue, 26 Aug 2025 16:33:57 +0200
From: Borislav Petkov <bp@...en8.de>
To: Yazen Ghannam <yazen.ghannam@....com>
Cc: x86@...nel.org, Tony Luck <tony.luck@...el.com>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
	Smita.KoralahalliChannabasappa@....com,
	Qiuxu Zhuo <qiuxu.zhuo@...el.com>,
	Nikolay Borisov <nik.borisov@...e.com>, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v5 05/20] x86/mce: Cleanup bank processing on init

On Tue, Aug 26, 2025 at 09:47:54AM -0400, Yazen Ghannam wrote:
> But I see how any inclusion counts:
> "Any further SoBs (Signed-off-by:'s) following the author's SoB are from
> people handling and transporting the patch..."

Yeah, that's the important point: each patch's SOB must document the path it
took from the author to the upstream kernel. That's why people who forward it
by adding it to their set or whatever else, must add their SOB for documenting
that they handled it on its way. Basically.

Thx.

-- 
Regards/Gruss,
    Boris.

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