From: Ping-Ke Shih <pkshih@realtek.com>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mehmet.fide@screeningeagle.com" <mehmet.fide@screeningeagle.com>
Subject: RE: [PATCH rtw-next v3 2/2] wifi: rtw88: support channel switch in AP mode
Date: Tue, 6 Oct 2026 07:54:54 +0000 [thread overview]
Message-ID: <3002971ac7824b0b9cafa852e0e81e8b@realtek.com> (raw)
In-Reply-To: <20261006074627.372751-1-mehmet.fide@gmail.com>
Mehmet Fide <mehmet.fide@gmail.com> wrote:
> > Will it be a problem just unconditionally initializing csa work?
>
> It was: a hardware restart replays add_interface() with the work still
> armed, and initialising it again would lose the pending timer. With the
> work in rtw_dev the question does not arise any more.
Can we stop the work properly before hardware restart?
I just don't want many flags (conditions).
Ping-Ke
next prev parent reply other threads:[~2026-10-06 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 14:35 [PATCH rtw-next v3 0/2] wifi: rtw88: channel switch in AP mode Mehmet Fide
2026-10-05 14:35 ` [PATCH rtw-next v3 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-05 17:36 ` Luka Gejak
2026-10-06 7:46 ` Mehmet Fide
2026-10-05 14:35 ` [PATCH rtw-next v3 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-05 17:33 ` [PATCH " Luka Gejak
2026-10-06 7:46 ` [PATCH rtw-next " Mehmet Fide
2026-10-06 1:26 ` Ping-Ke Shih
2026-10-06 7:46 ` Mehmet Fide
2026-10-06 7:54 ` Ping-Ke Shih [this message]
2026-10-06 8:16 ` Mehmet Fide
-- strict thread matches above, loose matches on Subject: below --
2026-10-05 14:33 [PATCH rtw-next v3 0/2] wifi: rtw88: " Mehmet Fide
2026-10-05 14:33 ` [PATCH rtw-next v3 2/2] wifi: rtw88: support " Mehmet Fide
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=3002971ac7824b0b9cafa852e0e81e8b@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.