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: <2025072108-yarn-sloping-5831@gregkh>
Date: Mon, 21 Jul 2025 08:28:03 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Vivek BalachandharTN <vivek.balachandhar@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [PATCH v2] staging: rtl8723bs: clean up redundant & parentheses

On Mon, Jul 21, 2025 at 06:14:12AM +0000, Vivek BalachandharTN wrote:
> Hi Greg,
> 
> Thanks again for your earlier feedback on the patch cleanup for rtw_mlme.c.
> 
> Since the original version included multiple checkpatch.pl fixes 
> (like spacing and formatting) and you suggested breaking them up by type, 
> 
> I wanted to ask:
> 
> For the remaining cleanups (e.g., spacing issues), should I submit them as:
> 
> separate standalone patches, or
> 
> as new versions (v2, v3, etc.) building on the current patch?
> 
> Just wanted to be sure I follow the preferred approach.

If you were on my side, recieving hundreds of patches a day to review,
what would you want to see?  :)

(hint, a patch series, properly versioned is the easiest.)

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ