From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
<linux-staging@lists.linux.dev>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michael Straube" <straube.linux@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Khushal Chitturi" <khushalchitturi@gmail.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Vivek BalachandharTN" <vivek.balachandhar@gmail.com>,
"Luka Gejak" <luka.gejak@linux.dev>,
"Ethan Tidmore" <ethantidmore06@gmail.com>,
"Artur Stupa" <arthur.stupa@gmail.com>,
"Zhuoheng Li" <lizhuoheng@kylinos.cn>,
"Nino Zhang" <ninozhang001@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: Reduce indentation in rtw_joinbss_event_prehandle
Date: Thu, 19 Mar 2026 09:04:05 +0100 [thread overview]
Message-ID: <DH6LPIGRIL2D.37YZEKWFQSMTD@linux.dev> (raw)
In-Reply-To: <20260318225550.535368-1-azpijr@gmail.com>
Hi Jose,
Thanks for this patch! Refactoring these deeply nested if-statements
makes the mlme flow much easier to read and maintain.
Functionally, the logic and lock handling look correct. Great catch on
removing the redundant spin_lock_bh(&pmlmepriv->lock) before the
function returns. That is a nice optimization of the original flow.
I have two minor notes for a v2:
1. Subject Line: The standard practice for staging is to use a
lowercase letter after the prefix. It should be: "staging: rtl8723bs:
reduce indentation..." instead of "Reduce".
2. Comment Typo: In the refactored step s3:
> + /* s3. find ptarget_wlan & update ptarget_sta after update
> + * cur_network only for station mode
> + */
The code here is calling rtw_joinbss_update_stainfo(), so the original
comment "find ptarget_sta" was actually correct. Since ptarget_wlan was
already found in s1, you might want to revert that word to avoid
confusion.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-03-19 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 22:55 [PATCH] staging: rtl8723bs: Reduce indentation in rtw_joinbss_event_prehandle Jose A. Perez de Azpillaga
2026-03-19 8:04 ` Luka Gejak [this message]
2026-03-19 8:11 ` 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=DH6LPIGRIL2D.37YZEKWFQSMTD@linux.dev \
--to=luka.gejak@linux.dev \
--cc=arthur.stupa@gmail.com \
--cc=azpijr@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=khushalchitturi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lizhuoheng@kylinos.cn \
--cc=ninozhang001@gmail.com \
--cc=straube.linux@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.