From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 3/3] netdev: hack back in disconnect event
Date: Tue, 5 Dec 2023 15:53:16 -0600 [thread overview]
Message-ID: <556a0e66-675c-486f-b02b-4b75e5294187@gmail.com> (raw)
In-Reply-To: <2f2871a4-faed-477a-b327-33d4355ec55f@gmail.com>
Hi James,
> They don't (only auth timeouts), but patches 1/2 add an associate timeout test.
Ah, I guess I should have looked at those too, whoops :)
>>
>> I wonder if we should make ft_associate use netdev_reassociate?
>
> So pass station_connect_cb into ft_associate, then to netdev? That seems
> reasonable.
>
Yep. Probably need a few additional checks to make sure we don't trigger any
offloading behavior.
Regards,
-Denis
prev parent reply other threads:[~2023-12-05 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 17:52 [PATCH 1/3] auto-t: add explicit stop() to IWD class James Prestwood
2023-12-05 17:52 ` [PATCH 2/3] auto-t: add association timeout test James Prestwood
2023-12-05 17:52 ` [PATCH 3/3] netdev: hack back in disconnect event James Prestwood
2023-12-05 21:37 ` Denis Kenzior
2023-12-05 21:45 ` James Prestwood
2023-12-05 21:53 ` 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=556a0e66-675c-486f-b02b-4b75e5294187@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