Received-SPF: pass (google.com: domain of linux-kernel+bounces-21277-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Date: Tue, 9 Jan 2024 10:56:51 -0800
From: Matthias Yee <mgyee9@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: fixed check alignment of open
 parenthesis in card.c
Message-ID: <ZZ2W85ap2aMBDi8F@mgyee-VirtualBox>
References: <20240109063618.2810-1-mgyee9@gmail.com>
 <cea37e85-cc21-498a-a09e-cfdaf7921844@moroto.mountain>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cea37e85-cc21-498a-a09e-cfdaf7921844@moroto.mountain>

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?

thanks,
matthias