linux-kernel - Re: [PATCH] staging: rtl8723bs: fix checkpatch issues in rtw

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: <aDbgqBKV-bIJXDjN@stanley.mountain>
Date: Wed, 28 May 2025 13:08:40 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Shawn Hua <shawnhuasz@...il.com>
Cc: linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
	gregkh@...uxfoundation.org, philipp.g.hortmann@...il.com,
	pkshih@...ltek.com, akpm@...ux-foundation.org,
	yixuanhuashawn@...keley.edu
Subject: Re: [PATCH] staging: rtl8723bs: fix checkpatch issues in
 rtw_pwrctrl.c

On Wed, May 28, 2025 at 05:19:14PM +0800, Shawn Hua wrote:
> This patch addresses several style issues in rtw_pwrctrl.c, as reported by checkpat
> ch.pl. I’ve fixed most warnings and errors, but left CamelCase and one type of CHECK unresolved.
> 
> I’m new to kernel development and submitting this for learning purposes. Please let me know if this type of patch is still helpful, or if it should be reworked or dropped.

Emails and patches should line wrap at 74 characters.

> 
> Best regards,
> Shawn Hua
> -----

Don't start your patch with an email, we don't want that in the git log.

> This patch fixes ~80 checkpatch.pl style issues, including spacing, indentation, and alignment.
> 
> Remaining issues:
> - CamelCase warnings were left unchanged to avoid breaking interface consistency across related files.
> - One CHECK regarding alignment with open parenthesis could not be resolved despite several attempts.

Don't list the things you haven't done.

> 
> No functional changes were made.
> 

This does too many things at once.  Also start with the latest code.
Some of these are already fixed.

regards,
dan carpenter