From: Ping-Ke Shih <pkshih@realtek.com>
To: Les Boys <lesboyspp43@outlook.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2] realtek/rtlwifi: ensure unicast is reinitialized to false in each iteration
Date: Tue, 25 Nov 2025 09:03:00 +0000 [thread overview]
Message-ID: <731806e542f245b3b3ae6d2429c499e5@realtek.com> (raw)
In-Reply-To: <SA2PR10MB4460861A8224AA99EE5ACF6BA6D1A@SA2PR10MB4460.namprd10.prod.outlook.com>
Les Boys <lesboyspp43@outlook.com> wrote:
> Previously, the unicast variable was only initialized once during the
> function execution. Therefore, if unicast was set to true in the (n-1)th
> iteration, it would affect the nth iteration. This patch resolves the issue
> by reinitializing unicast to false at the start of each iteration.
>
> CHANGE:
> 1. Fix indention
> 2. Use a better way recommanded by maintainer to solve original problem
> 3. Fix subject
> 4. Remove useless if and TODO comment
>
> (added CC this time)
>
> Signed-off-by: LBLaiSiNanHai <lesboyspp43@outlook.com>
This should be your real name which is identical to From field
(I have mentioned this in v1).
---
Move your CHANGE here with three '-' as delimiter
> ---
> drivers/net/wireless/realtek/rtlwifi/pci.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtlwifi/pci.c b/drivers/net/wireless/realtek/rtlwifi/pci.c
> index fe7140328..a07de6b57 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/pci.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/pci.c
> @@ -752,16 +752,13 @@ static void _rtl_pci_rx_interrupt(struct ieee80211_hw *hw)
> memcpy(IEEE80211_SKB_RXCB(skb), &rx_status,
> sizeof(rx_status));
>
> - unicast = false;
This is your change in v1, please use upstream as base.
Also, you missed to remove initializer of `unicast` in original code.
More, check status of your patch in patchwork [1].
[1] https://patchwork.kernel.org/project/linux-wireless/patch/SA2PR10MB4460861A8224AA99EE5ACF6BA6D1A@SA2PR10MB4460.namprd10.prod.outlook.com/
> -
> - if (is_broadcast_ether_addr(hdr->addr1)) {
> - ;/*TODO*/
> - } else if (is_multicast_ether_addr(hdr->addr1)) {
> - ;/*TODO*/
> - } else {
> + if (is_unicast_ether_addr(hdr->addr1)) {
> unicast = true;
> rtlpriv->stats.rxbytesunicast += skb->len;
> + } else {
> + unicast = false;
> }
> +
> rtl_is_special_data(hw, skb, false, true);
>
> if (ieee80211_is_data(fc)) {
> --
> 2.44.0
next prev parent reply other threads:[~2025-11-25 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:00 [PATCH v1] " Les Boys
2025-11-25 7:23 ` Ping-Ke Shih
[not found] ` <SA2PR10MB44605A853386FE1BB7174498A6D1A@SA2PR10MB4460.namprd10.prod.outlook.com>
2025-11-25 8:34 ` [PATCH rtw-next v2] " Les Boys
2025-11-25 9:03 ` Ping-Ke Shih [this message]
2025-11-25 11:43 ` [PATCH rtw-next v3] realtek/rtlwifi: remove unused two if blocks and put unicast set inner if and else block Les Boys
2025-11-26 0:47 ` Ping-Ke Shih
2025-11-26 5:55 ` [PATCH rtw-next v4] " Les Boys
2025-11-26 8:54 ` Ping-Ke Shih
2025-11-26 9:19 ` 回复: [PATCH rtw-next v5] realtek: rtlwifi: remove dead code and ensure unicast is always set explicitly in every iteration Les Boys
2025-11-26 9:34 ` Ping-Ke Shih
2025-12-23 5:21 ` Ping-Ke Shih
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=731806e542f245b3b3ae6d2429c499e5@realtek.com \
--to=pkshih@realtek.com \
--cc=lesboyspp43@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®