From: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>
To: Nicolas Escande <nico.escande@gmail.com>,
Kalle Valo <kvalo@kernel.org>, Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] wifi: ath12k: handle change_vif_links() callback
Date: Tue, 4 Feb 2025 22:49:52 +0530 [thread overview]
Message-ID: <c032881a-153e-496f-bea2-0eb8452ad495@oss.qualcomm.com> (raw)
In-Reply-To: <D7JLLQ79FP2Z.2Z7VYLSC52A2U@gmail.com>
On 2/4/25 16:14, Nicolas Escande wrote:
> On Tue Feb 4, 2025 at 11:23 AM CET, Aditya Kumar Singh wrote:
>> On 2/4/25 15:32, Nicolas Escande wrote:
>>> Hello,
>>>
>>> When applying this series I am no longer able to start an AP on a DFS channel.
>>> (I don't know specifically which patch though)
>>>
>>
>> Thanks for reporting this. I think non-DFS channel should be working
>> fine right?
> Right non DFS channels are ok, only DFS ones, and not from the get go but after
> the initial CAC, when they switch to operational mode.
>>
>> Anyways, I'm able to repro the issue locally. Let me investigate further
>> and come back.
> I'll happily test what you can throw at me.
:)
I have posted v2 [1] fixing the reported DFS issue as well. When you
have time, could you test and confirm? Locally I'm able to see
DFS/non-DFS working fine now.
[1]:
https://lore.kernel.org/linux-wireless/20250204-unlink_link_arvif_from_chanctx-v2-0-764fb5973c1a@oss.qualcomm.com/
--
Aditya
prev parent reply other threads:[~2025-02-04 17:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 4:23 [PATCH 0/8] wifi: ath12k: handle change_vif_links() callback Aditya Kumar Singh
2025-02-04 4:23 ` [PATCH 1/8] wifi: ath12k: eliminate redundant debug mask check in ath12k_dbg() Aditya Kumar Singh
2025-02-04 7:35 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 2/8] wifi: ath12k: introduce ath12k_generic_dbg() Aditya Kumar Singh
2025-02-04 7:35 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 3/8] wifi: ath12k: remove redundant vif settings during link interface creation Aditya Kumar Singh
2025-02-04 7:35 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 4/8] wifi: ath12k: remove redundant logic for initializing arvif Aditya Kumar Singh
2025-02-04 7:35 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 5/8] wifi: ath12k: use arvif instead of link_conf in ath12k_mac_set_key() Aditya Kumar Singh
2025-02-04 7:36 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 6/8] wifi: ath12k: relocate a few functions in mac.c Aditya Kumar Singh
2025-02-04 7:36 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 7/8] wifi: ath12k: allocate new links in change_vif_links() Aditya Kumar Singh
2025-02-04 7:36 ` Vasanthakumar Thiagarajan
2025-02-04 4:23 ` [PATCH 8/8] wifi: ath12k: handle link removal " Aditya Kumar Singh
2025-02-04 7:37 ` Vasanthakumar Thiagarajan
2025-02-04 10:02 ` [PATCH 0/8] wifi: ath12k: handle change_vif_links() callback Nicolas Escande
2025-02-04 10:23 ` Aditya Kumar Singh
2025-02-04 10:44 ` Nicolas Escande
2025-02-04 17:19 ` Aditya Kumar Singh [this message]
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=c032881a-153e-496f-bea2-0eb8452ad495@oss.qualcomm.com \
--to=aditya.kumar.singh@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.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