From: Mehmet Fide <mehmet.fide@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH rtw-next v2 2/2] wifi: rtw88: support channel switch in AP mode
Date: Mon, 5 Oct 2026 11:51:16 +0200 [thread overview]
Message-ID: <20261005095116.22186-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <135e11c2a24642d0af774d6fd3c7f5a2@realtek.com>
Hi Ping-Ke,
On 2026-10-05 Ping-Ke Shih wrote:
> Should we define csa_beacon_work by vif? Then, here we can get rtwvif
> (and vif) from work context.
Yes, v3 moves it into struct rtw_vif; the ad-hoc check and the wrapper
go with it, as do the comments. The hw scan refusal is in the last
paragraph of the message already, so I take it the inline comment is
what should go; done too.
v3 follows once the hardware scan path has run on an RTL8822CU, whose
firmware has scan offload; the dongle is on its way here.
Best regards,
Mehmet
prev parent reply other threads:[~2026-10-05 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 7:44 [PATCH rtw-next v2 0/2] wifi: rtw88: " Mehmet Fide
2026-09-30 7:44 ` [PATCH rtw-next v2 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-01 7:16 ` [PATCH " Luka Gejak
2026-10-01 11:54 ` [PATCH rtw-next " Mehmet Fide
2026-10-05 2:49 ` Ping-Ke Shih
2026-09-30 7:44 ` [PATCH rtw-next v2 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-01 7:18 ` [PATCH " Luka Gejak
2026-10-01 11:54 ` [PATCH rtw-next " Mehmet Fide
2026-10-05 3:11 ` Ping-Ke Shih
2026-10-05 9:51 ` Mehmet Fide [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=20261005095116.22186-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=mehmet.fide@screeningeagle.com \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@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
all inboxes | Powered by JetHome®