linux-kernel - Re: [PATCH v1 1/2] EDAC/bluefield: fix white space in bluefield_edac_mc

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: <20240613151129.GIZmsMIc1lXDXJf65u@fat_crate.local>
Date: Thu, 13 Jun 2024 17:11:29 +0200
From: Borislav Petkov <bp@...en8.de>
To: David Thompson <davthompson@...dia.com>
Cc: "tony.luck@...el.com" <tony.luck@...el.com>,
	"james.morse@....com" <james.morse@....com>,
	"mchehab@...nel.org" <mchehab@...nel.org>,
	"rric@...nel.org" <rric@...nel.org>,
	Shravan Ramani <shravankr@...dia.com>,
	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 1/2] EDAC/bluefield: fix white space in
 bluefield_edac_mc_probe

On Thu, Jun 13, 2024 at 03:06:38PM +0000, David Thompson wrote:
> I did review this section of the kernel documentation and then
> went on to create a v2 with the updated commit message.
> I apologize but I didn't notice your comment below about 
> your preference to not have this type of patch at all.  I have been
> told in the past to have separate patches for style cleanups, and

Yeah, it all depends on the maintainer. I, personally, do not encourage style
cleanups only because they interfere with git archeology and teach new
submitters not to chase real bugs but do silly patches only.

> not to bundle them with features.  But I can do as you recommend for next
> version.  I will squash the two style fixes into a patch that contains some
> new functionality for the BlueField EDAC driver.

Thanks.

Simply use checkpatch on your patches only but not on the .c files directly. 

-- 
Regards/Gruss,
    Boris.

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