linux-kernel - Re: [PATCH] staging: vt6655: fixed check alignment of open parenthesis in card.c

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: <2024010920-flatworm-storage-5690@gregkh>
Date: Tue, 9 Jan 2024 20:10:24 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Matthias Yee <mgyee9@...il.com>
Cc: Dan Carpenter <dan.carpenter@...aro.org>, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: vt6655: fixed check alignment of open
 parenthesis in card.c

On Tue, Jan 09, 2024 at 10:56:51AM -0800, Matthias Yee wrote:
> On Tue, Jan 09, 2024 at 11:22:42AM +0300, Dan Carpenter wrote:
> > On Mon, Jan 08, 2024 at 10:36:19PM -0800, Matthias Yee wrote:
> > > This patch adjusts whitespace to fix the checkpatch warning Alignment Should Match Open Parenthesis.
> > > 
> > 
> > Line wrap your commit message at 75 characters, and also run checkpatch.pl
> > on your patches.  Otherwise it's okay by me.
> > 
> 
> Sounds good, will do. However, checkpatch.pl gives an avoid CamelCase
> warning. Is it okay to ignore if I am only focusing on the parenthesis
> alignment warning in this patch?

Yes.