[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2026012454-perish-operable-aeba@gregkh>
Date: Sat, 24 Jan 2026 07:51:05 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Michael Huang <tehsiu.huang@...il.com>
Cc: linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] staging: rtl8723bs: cleanup and indentation
refactoring
On Fri, Jan 23, 2026 at 01:19:02PM -0800, Michael Huang wrote:
> This series improves the code quality and readability of rtw_mlme_ext.c
> in the rtl8723bs driver.
>
> The first patch refactors several deeply nested loops and if-statements
> by using guard clauses (continue statements). This flattens the logic
> and makes the code easier to follow.
>
> The second patch addresses various style issues reported by
> checkpatch.pl, including line length exceeding 100 columns,
> unnecessary parentheses, and unnecessary braces.
>
> Michael Huang (2):
> staging: rtl8723bs: refactor nested loops to reduce indentation
> staging: rtl8723bs: fix line length and coding style issues
>
> drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 142 ++++++++++--------
> 1 file changed, 80 insertions(+), 62 deletions(-)
>
> --
> 2.43.0
>
>
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:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
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
Powered by blists - more mailing lists