From: Nikolay Kulikov <nikolayof23@gmail.com>
To: Gabriel Windlin <gawindlin@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrei Khomenkov <khomenkov@mailbox.org>,
Khasar Munkh-Erdene <02khasar@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove unneeded else after return in enqueue_reorder_recvframe()
Date: Mon, 7 Sep 2026 10:31:22 +0300 [thread overview]
Message-ID: <ap5oSuo4v9ZZaHeY@archlinux> (raw)
In-Reply-To: <20260906233552.971860-1-gawindlin@gmail.com>
On Mon, Sep 07, 2026 at 01:35:43AM +0200, Gabriel Windlin wrote:
> In enqueue_reorder_recvframe(), checkpatch warns that 'else is not
> generally useful after a break or return'. The duplicate packet check
> returns false, making the following else on break redundant.
>
> Simplify the loop control flow by using continue when advancing the
> list and eliminating the unneeded else statement.
>
> Signed-off-by: Gabriel Windlin <gawindlin@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_recv.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
> index 7568fc514d7c..498c7273f273 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))
> + if (SN_LESS(pnextattrib->seq_num, pattrib->seq_num)) {
> plist = get_next(plist);
> - else 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); */
> + continue;
> + }
> +
> + if (SN_EQUAL(pnextattrib->seq_num, pattrib->seq_num))
> return false;
> - else
> - break;
> +
> + break;
> }
Hi,
there is already a similar patch in the lore:
https://lore.kernel.org/linux-staging/20260820162601.74952-1-myeonghyeon.park@gmail.com/T/
prev parent reply other threads:[~2026-09-07 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 23:35 Gabriel Windlin
2026-09-07 7:31 ` Nikolay Kulikov [this message]
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=ap5oSuo4v9ZZaHeY@archlinux \
--to=nikolayof23@gmail.com \
--cc=02khasar@gmail.com \
--cc=gawindlin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=khomenkov@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
all inboxes | Powered by JetHome®