From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Nicolas Escande" <nico.escande@gmail.com>, <ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath12k: fbx: Add missing htt_metadata flag in ath12k_dp_tx()
Date: Sat, 25 Jan 2025 21:23:19 +0100 [thread overview]
Message-ID: <D7BFNSFK7P2Y.1MHPLEN8MNDLC@gmail.com> (raw)
In-Reply-To: <20250124113331.93476-1-nico.escande@gmail.com>
On Fri Jan 24, 2025 at 12:33 PM CET, Nicolas Escande wrote:
> When AP-VLAN was added, we did not add HTT_TCL_META_DATA_VALID_HTT flag to
> the tx_info's meta_data_flags . Without this flag the firmware seems to
> reject all the broadcast (ap-vlan) frames. So lets add it same as ath11k
> did it in commit 5e8a373c8699 ("ath11k: Add support for dynamic vlan")
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1
>
> Fixes: 26dd8ccdba4d ("wifi: ath12k: dynamic VLAN support")
> Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
I left a 'fbx' in the title that needs to be removed here. I'll send a v2 if
need be, but feel free to remove it yourselves if you take the patch as is.
next prev parent reply other threads:[~2025-01-25 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 11:33 [PATCH] wifi: ath12k: fbx: Add missing htt_metadata flag in ath12k_dp_tx() Nicolas Escande
2025-01-25 20:23 ` Nicolas Escande [this message]
2025-02-12 4:07 ` Vasanthakumar Thiagarajan
2025-02-12 4:09 ` Vasanthakumar Thiagarajan
2025-02-19 17:58 ` Jeff Johnson
2025-02-19 18:33 ` Nicolas Escande
2025-02-20 15:18 ` Jeff Johnson
2025-02-20 15:46 ` Jeff Johnson
2025-02-20 17:49 ` Nicolas Escande
2025-02-20 21:40 ` 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=D7BFNSFK7P2Y.1MHPLEN8MNDLC@gmail.com \
--to=nico.escande@gmail.com \
--cc=ath12k@lists.infradead.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