From: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
To: Sushant Butta <sushant.butta@oss.qualcomm.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath-next 0/2] wifi: ath12k: correct monitor-mode RX metadata handling
Date: Mon, 29 Jun 2026 09:44:37 +0530 [thread overview]
Message-ID: <af592fed-313a-4bc0-a4b3-f04ca0ffa6fe@oss.qualcomm.com> (raw)
In-Reply-To: <20260609064856.547032-1-sushant.butta@oss.qualcomm.com>
On 6/9/2026 12:18 PM, Sushant Butta wrote:
> This series fixes monitor-mode meta data handling in ath12k and trims dead code:
>
> Monitor mode delivers raw 802.11 frames should not set RX_FLAG_8023 flag,
> and populate peer/link metadata in ieee80211_rx_status for monitor MSDUs.
>
> Sushant Butta (2):
> wifi: ath12k: Skip setting RX_FLAG_8023 for Ethernet-II (DIX) frames
> in monitor mode
> wifi: ath12k: Skip peer link info update in rx_status for monitor
> MSDUs
>
> drivers/net/wireless/ath/ath12k/dp_mon.c | 70 +------------------
> drivers/net/wireless/ath/ath12k/dp_mon.h | 4 +-
> .../net/wireless/ath/ath12k/wifi7/dp_mon.c | 7 +-
> 3 files changed, 4 insertions(+), 77 deletions(-)
>
>
Reviewed-by: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
next prev parent reply other threads:[~2026-06-29 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 6:48 [PATCH ath-next 0/2] wifi: ath12k: correct monitor-mode RX metadata handling Sushant Butta
2026-06-09 6:48 ` [PATCH ath-next 1/2] wifi: ath12k: Skip setting RX_FLAG_8023 for Ethernet-II (DIX) frames in monitor mode Sushant Butta
2026-06-09 6:48 ` [PATCH ath-next 2/2] wifi: ath12k: Skip peer link info update in rx_status for monitor MSDUs Sushant Butta
2026-06-29 2:05 ` [PATCH ath-next 0/2] wifi: ath12k: correct monitor-mode RX metadata handling Baochen Qiang
2026-06-29 4:14 ` Rameshkumar Sundaram [this message]
2026-06-30 21:26 ` Jeff Johnson
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=af592fed-313a-4bc0-a4b3-f04ca0ffa6fe@oss.qualcomm.com \
--to=rameshkumar.sundaram@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sushant.butta@oss.qualcomm.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