From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "myeonghyeon.park" <myeonghyeon.park@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: reorder conditions to avoid else branch
Date: Thu, 20 Aug 2026 19:10:16 +0200 [thread overview]
Message-ID: <2026082057-pastrami-juncture-7030@gregkh> (raw)
In-Reply-To: <20260820162601.74952-1-myeonghyeon.park@gmail.com>
On Fri, Aug 21, 2026 at 01:26:01AM +0900, myeonghyeon.park wrote:
> Fix the checkpatch.pl warning:
>
> "WARNING: else is not generally useful after a break or return"
>
> in core/rtw_recv.c.
>
> Return early when the SN_EQUAL() condition is met and break when
> SN_LESS() condition is false to eliminate the unnecessary else branch.
>
> Signed-off-by: myeonghyeon.park <myeonghyeon.park@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_recv.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
> diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
> index 7568fc514d7c..5776d0212ab8 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_recv.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_recv.c
> @@ -1782,14 +1782,15 @@ static int enqueue_reorder_recvframe(struct recv_reorder_ctrl *preorder_ctrl, un
> pnextrframe = (union recv_frame *)plist;
> pnextattrib = &pnextrframe->u.hdr.attrib;
>
> - if (SN_LESS(pnextattrib->seq_num, pattrib->seq_num))
> - plist = get_next(plist);
> - else if (SN_EQUAL(pnextattrib->seq_num, pattrib->seq_num))
> + if (SN_EQUAL(pnextattrib->seq_num, pattrib->seq_num))
> /* Duplicate entry is found!! Do not insert current entry. */
> /* spin_unlock_irqrestore(&ppending_recvframe_queue->lock, irql); */
> return false;
> - else
> +
> + if (!SN_LESS(pnextattrib->seq_num, pattrib->seq_num))
> break;
> +
> + plist = get_next(plist);
> }
>
> /* spin_lock_irqsave(&ppending_recvframe_queue->lock, irql); */
> --
> 2.52.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:
- It looks like you did not use your "real" name for the patch on either
the Signed-off-by: line, or the From: line (both of which have to
match). Please read the kernel file,
Documentation/process/submitting-patches.rst for how to do this
correctly.
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
next prev parent reply other threads:[~2026-08-20 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 16:26 [PATCH] staging: rtl8723bs: reorder conditions to avoid else branch myeonghyeon.park
2026-08-20 17:10 ` Greg Kroah-Hartman [this message]
2026-08-20 18:53 ` Dan Carpenter
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=2026082057-pastrami-juncture-7030@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=myeonghyeon.park@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