From: Bob Copeland <me@bobcopeland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 7/7] wmediumd: don't treat management frames as noack
Date: Mon, 23 Mar 2020 15:08:31 -0400 [thread overview]
Message-ID: <20200323190831.GB5207@bobcopeland.com> (raw)
In-Reply-To: <20200323162245.19716cc94db4.Ib4a8bb12802840a3b9ed7e2e9ca1748a4e77e6ee@changeid>
On Mon, Mar 23, 2020 at 04:25:42PM +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> It's incorrect to treat management frames as noack, they're
> retransmitted just like any other frame; fix this.
I think it was just a hack to make mesh paths establish even
if snr was terrible, obviously not realistic. Thanks!
--
Bob Copeland %% https://bobcopeland.com/
next prev parent reply other threads:[~2020-03-23 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 15:25 [PATCH 0/7] more wmediumd updates Johannes Berg
2020-03-23 15:25 ` [PATCH 1/7] wmediumd: mark various functions static Johannes Berg
2020-03-23 15:25 ` [PATCH 2/7] wmediumd: pass actual signal to hwsim Johannes Berg
2020-03-23 15:25 ` [PATCH 3/7] wmediumd: fix use-after-free Johannes Berg
2020-03-23 15:25 ` [PATCH 4/7] wmediumd: add a unix-domain control socket Johannes Berg
2020-03-23 15:25 ` [PATCH 5/7] wmediumd: support compilation with asan/ubsan Johannes Berg
2020-03-23 15:25 ` [PATCH 6/7] wmediumd: track dynamic station addresses Johannes Berg
2020-03-23 15:25 ` [PATCH 7/7] wmediumd: don't treat management frames as noack Johannes Berg
2020-03-23 19:08 ` Bob Copeland [this message]
2020-03-23 20:12 ` Johannes Berg
2020-03-23 20:37 ` Bob Copeland
2020-03-23 19:11 ` [PATCH 0/7] more wmediumd updates Bob Copeland
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=20200323190831.GB5207@bobcopeland.com \
--to=me@bobcopeland.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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).