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 v4] realtek/rtlwifi: remove unused two if blocks and put unicast set inner if and else block
Date: Wed, 26 Nov 2025 08:54:07 +0000 [thread overview]
Message-ID: <77827732646345698e1bf133bbc87494@realtek.com> (raw)
In-Reply-To: <SA2PR10MB4460E7C842251428DB9D253EA6DEA@SA2PR10MB4460.namprd10.prod.outlook.com>
Les Boys <lesboyspp43@outlook.com> wrote:
> Removed unused if blocks and put the unicast set sentence into the
> if/else block.
Commit message is always to explain why we need this patch, but this
describes what this patch changes.
I think subject and commit message of v1 is more suitable than v4.
More, v5 subject should be "[PATCH rtw-next v5] wifi: rtlwifi: ..."
(please just copy & paste)
Otherwise, patch content is fine to me.
>
> Signed-off-by: Les Boys <lesboyspp43@outlook.com>
> ---
> CHANGE:
> 1. Move change block to correct location;
> 2. Removed initalization of unicast on the begin of function.
> ---
> drivers/net/wireless/realtek/rtlwifi/pci.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtlwifi/pci.c b/drivers/net/wireless/realtek/rtlwifi/pci.c
> index d08046926..eda3b80df 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/pci.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/pci.c
> @@ -652,7 +652,7 @@ static void _rtl_pci_rx_interrupt(struct ieee80211_hw *hw)
> unsigned int count = rtlpci->rxringcount;
> u8 own;
> u8 tmp_one;
> - bool unicast = false;
> + bool unicast;
> u8 hw_queue = 0;
> unsigned int rx_remained_cnt = 0;
> struct rtl_stats stats = {
> @@ -752,14 +752,13 @@ static void _rtl_pci_rx_interrupt(struct ieee80211_hw *hw)
> memcpy(IEEE80211_SKB_RXCB(skb), &rx_status,
> sizeof(rx_status));
>
> - 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-26 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:00 [PATCH v1] realtek/rtlwifi: ensure unicast is reinitialized to false in each iteration 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
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 [this message]
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=77827732646345698e1bf133bbc87494@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;
as well as URLs for NNTP newsgroup(s).