From: hyperfekt <linux-wireless@hyperfekt.net>
To: hyperfekt <linux-wireless@hyperfekt.net>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
luca@coelho.fi
Subject: (No Subject)
Date: Fri, 22 May 2020 18:18:38 +0000 [thread overview]
Message-ID: <20200522181832.13840-1-linux-wireless@hyperfekt.net> (raw)
In-Reply-To: <20200519095732.16268-1-linux-wireless@hyperfekt.net>
Subject: Re: [PATCH 8/8] mac80211: IBSS: send deauth when expiring inactive STAs
After running a kernel without the patch some more, I can say that that only
seems to reduce the frequency of the lockups, instead of eliminating them.
I don't really feel capable of debugging this on my own, but the last kernel
version this problem does not occur on is 5.3.
next prev parent reply other threads:[~2020-05-22 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 9:57 [PATCH 8/8] mac80211: IBSS: send deauth when expiring inactive STAs linux-wireless
2020-05-22 18:18 ` hyperfekt [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-01 7:56 (no subject) Dan Carpenter
2011-05-01 8:02 ` Dan Carpenter
2008-01-04 14:00 Cristian
2007-07-18 4:09 Glenn
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=20200522181832.13840-1-linux-wireless@hyperfekt.net \
--to=linux-wireless@hyperfekt.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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;
as well as URLs for NNTP newsgroup(s).