From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 1/4] netdev: check connected in channel switch event
Date: Wed, 20 Aug 2025 11:20:13 -0500 [thread overview]
Message-ID: <efd97b52-0b85-4429-8760-01ae21b5d04f@gmail.com> (raw)
In-Reply-To: <20250818143041.283887-1-prestwoj@gmail.com>
Hi James,
On 8/18/25 9:30 AM, James Prestwood wrote:
> In an ideal world userspace should never be getting a channel switch
> event unless connected to an AP, but alas this has been seen at least
> with ath10k hardware. This causes IWD to crash since the logic
> assumes netdev->handshake is set.
> ---
> src/netdev.c | 3 +++
> 1 file changed, 3 insertions(+)
>
All applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2025-08-20 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 14:30 [PATCH v2 1/4] netdev: check connected in channel switch event James Prestwood
2025-08-18 14:30 ` [PATCH v2 2/4] netdev: disconnect rather than deauth in FT association failure James Prestwood
2025-08-18 14:30 ` [PATCH v2 3/4] auto-t: make waiting for channel switch configurable James Prestwood
2025-08-18 14:30 ` [PATCH v2 4/4] auto-t: add test for channel switch during roam James Prestwood
2025-08-20 16:20 ` Denis Kenzior [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=efd97b52-0b85-4429-8760-01ae21b5d04f@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@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