From: Ahmet Zeren via B4 Relay <devnull+niko3x.proton.me@kernel.org>
To: Jes Sorensen <Jes.Sorensen@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Ping-Ke Shih <pkshih@realtek.com>,
Ahmet Zeren <niko3x@proton.me>
Subject: [PATCH rtw-next v2 1/2] wifi: rtl8xxxu: don't report frames sent without ACK as acked
Date: Sun, 22 Nov 2026 09:00:38 +0300 [thread overview]
Message-ID: <20261122-b4-tx-status-v2-1-bbfdbd880acf@proton.me> (raw)
In-Reply-To: <20261122-b4-tx-status-v2-0-bbfdbd880acf@proton.me>
From: Ahmet Zeren <niko3x@proton.me>
Every frame whose USB transfer succeeded is reported as acked, including
those sent with IEEE80211_TX_CTL_NO_ACK. Report these as
IEEE80211_TX_STAT_NOACK_TRANSMITTED instead.
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
Signed-off-by: Ahmet Zeren <niko3x@proton.me>
---
drivers/net/wireless/realtek/rtl8xxxu/core.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/realtek/rtl8xxxu/core.c b/drivers/net/wireless/realtek/rtl8xxxu/core.c
index 604bb1e5b05..ab2818986cc 100644
--- a/drivers/net/wireless/realtek/rtl8xxxu/core.c
+++ b/drivers/net/wireless/realtek/rtl8xxxu/core.c
@@ -5167,8 +5167,12 @@ static void rtl8xxxu_tx_complete(struct urb *urb)
tx_info->status.rates[0].idx = -1;
tx_info->status.rates[0].count = 0;
- if (!urb->status)
- tx_info->flags |= IEEE80211_TX_STAT_ACK;
+ if (!urb->status) {
+ if (tx_info->flags & IEEE80211_TX_CTL_NO_ACK)
+ tx_info->flags |= IEEE80211_TX_STAT_NOACK_TRANSMITTED;
+ else
+ tx_info->flags |= IEEE80211_TX_STAT_ACK;
+ }
ieee80211_tx_status_irqsafe(hw, skb);
--
2.56.1
next prev parent reply other threads:[~2026-11-22 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 6:00 [PATCH rtw-next v2 0/2] wifi: rtl8xxxu: report real TX status on RTL8188CU/RTL8192CU Ahmet Zeren via B4 Relay
2026-11-22 6:00 ` Ahmet Zeren via B4 Relay [this message]
2026-11-22 6:00 ` [PATCH rtw-next v2 2/2] " Ahmet Zeren via B4 Relay
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=20261122-b4-tx-status-v2-1-bbfdbd880acf@proton.me \
--to=devnull+niko3x.proton.me@kernel.org \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=niko3x@proton.me \
--cc=pkshih@realtek.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
all inboxes | Powered by JetHome®