From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 1/3] station/wsc: remove beacon loss handling
Date: Wed, 04 Nov 2020 13:41:21 -0600 [thread overview]
Message-ID: <e72bbb0e-89f3-b38f-fbda-84f558368cca@gmail.com> (raw)
In-Reply-To: <20201103205129.2744888-1-prestwoj@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Hi James,
On 11/3/20 2:51 PM, James Prestwood wrote:
> Modern kernels ~5.4+ have changed the way lost beacons are
> reported and effectively make the lost beacon event useless
> because it is immediately followed by a disconnect event. This
> does now allow IWD enough time to do much of anything before
> the disconnect comes in and we are forced to fully re-connect
> to a different AP.
> ---
> src/station.c | 26 --------------------------
> src/wsc.c | 3 ---
> 2 files changed, 29 deletions(-)
>
All applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2020-11-04 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 20:51 [PATCH 1/3] station/wsc: remove beacon loss handling James Prestwood
2020-11-03 20:51 ` [PATCH 2/3] netdev: remove handling of beacon loss event James Prestwood
2020-11-03 20:51 ` [PATCH 3/3] auto-t: remove beacon loss tests James Prestwood
2020-11-04 19:41 ` 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=e72bbb0e-89f3-b38f-fbda-84f558368cca@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.org \
/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.