Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Vivek BalachandharTN <vivek.balachandhar@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v2] staging: rtl8723bs: clean up redundant & parentheses
Date: Mon, 21 Jul 2025 08:28:03 +0200	[thread overview]
Message-ID: <2025072108-yarn-sloping-5831@gregkh> (raw)
In-Reply-To: <20250721061412.297554-1-vivek.balachandhar@gmail.com>

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

  reply	other threads:[~2025-07-21  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-20  8:33 [PATCH] staging: rtl8723bs: remove unnecessary parentheses around address-of operators Vivek BalachandharTN
2025-07-20  8:37 ` Greg KH
2025-07-20  9:21 ` [PATCH v2] staging: rtl8723bs: clean up redundant & parentheses Vivek BalachandharTN
2025-07-21  6:14   ` Vivek BalachandharTN
2025-07-21  6:28     ` Greg KH [this message]
2025-07-21  6:56     ` Vivek BalachandharTN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025072108-yarn-sloping-5831@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=vivek.balachandhar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox