From: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.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: Wed, 12 Feb 2025 09:39:15 +0530 [thread overview]
Message-ID: <03697f42-7237-9ea0-311b-ed0cc5ac4e7e@oss.qualcomm.com> (raw)
In-Reply-To: <48cea2db-c6a7-63f1-5e3c-1db77a6fb84e@oss.qualcomm.com>
On 2/12/2025 9:37 AM, Vasanthakumar Thiagarajan wrote:
>
>
> On 1/24/2025 5:03 PM, 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>
>
> Thanks for the this.
My bad, I meant "Thanks for the fix"
next prev parent reply other threads:[~2025-02-12 4:11 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
2025-02-12 4:07 ` Vasanthakumar Thiagarajan
2025-02-12 4:09 ` Vasanthakumar Thiagarajan [this message]
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=03697f42-7237-9ea0-311b-ed0cc5ac4e7e@oss.qualcomm.com \
--to=vasanthakumar.thiagarajan@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nico.escande@gmail.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