Re: [PATCH v2 0/5] staging: rtl8723bs: clean up coding style in rtw_mlme_ext

[Greg KH <gregkh@linuxfoundation.org>]

On Wed, Jul 08, 2026 at 01:14:45AM +0800, Jinke Wu wrote:
> This patch series splits the original v1 patch into a 5-part series
> to properly isolate different types of coding style cleanups, as
> requested during the v1 review.
> 
> To keep each patch strictly focused on a single logical change:
> 1. Patch 1 fixes the operator spacing warnings.
> 2. Patch 2 resolves the line length and alignment issues that were
>    consequently introduced or exposed by the spacing fixes in Patch 1.
> 3. Patches 3, 4, and 5 clean up other style issues (nested assignments,
>    parentheses, boolean checks) within the same affected code blocks.
> 
> By structuring the series this way, each patch achieves 100% historical
> purity without interfering with unrelated parts of the file.
> 
> Changes in v2:
> - Split the omnibus v1 patch into 5 dedicated, standalone patches.
> 
> Jinke Wu (5):
>   staging: rtl8723bs: fix operator spacing in rtw_mlme_ext
>   staging: rtl8723bs: fix line length and alignment in rtw_mlme_ext
>   staging: rtl8723bs: split nested assignment in OnAssocRsp
>   staging: rtl8723bs: remove unnecessary parentheses in issue_asocrsp
>   staging: rtl8723bs: simplify boolean comparison in send_beacon
> 
>  drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 227 ++++++++++--------
>  1 file changed, 126 insertions(+), 101 deletions(-)


Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch did not apply to any known trees that Greg is in control
  of.  Possibly this is because you made it against Linus's tree, not
  the linux-next tree, which is where all of the development for the
  next version of the kernel is at.  Please refresh your patch against
  the linux-next tree, or even better yet, the development tree
  specified in the MAINTAINERS file for the subsystem you are submitting
  a patch for, and resend it.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot