From: Johannes Berg <johannes@sipsolutions.net>
To: "Lazar, Alexei Avshalom" <ailizaro@codeaurora.org>,
Kalle Valo <kvalo@codeaurora.org>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, wil6210@qca.qualcomm.com
Subject: Re: [PATCH v3] cfg80211: add set/get link loss profile
Date: Wed, 29 Mar 2017 11:01:21 +0200 [thread overview]
Message-ID: <1490778081.7948.17.camel@sipsolutions.net> (raw)
In-Reply-To: <62127d4a-db9f-ab77-fb86-17d92b0ce81d@codeaurora.org>
On Mon, 2017-03-06 at 15:54 +0200, Lazar, Alexei Avshalom wrote:
>
> The supported values are:
[...]
Regardless of the documentation, I think this is a bit fishy. Why
bother with this to start with?
We once had two patches (that we ultimately gave up on) doing something
similar but simply letting userspace decide. This was centered on
mac80211's beacon loss "link loss detection", but could easily be
generalized a little bit more:
https://p.sipsolutions.net/3a594dead519b4b2.txt
https://p.sipsolutions.net/100ce7df53692daa.txt
Perhaps with some adjustments such an approach would be workable for
you?
johannes
next prev parent reply other threads:[~2017-03-29 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 11:33 cfg80211: add set/get link loss profile Lazar, Alexei Avshalom
2016-11-10 13:55 ` Kalle Valo
2016-11-17 13:50 ` Lazar, Alexei Avshalom
2016-11-18 11:05 ` Kalle Valo
2016-12-19 10:58 ` Lazar, Alexei Avshalom
2016-12-19 10:58 ` [PATCH v2] " Lazar, Alexei Avshalom
2016-12-20 17:00 ` Dan Williams
2017-03-06 13:54 ` [PATCH v3] " Lazar, Alexei Avshalom
2017-03-29 9:01 ` Johannes Berg [this message]
2016-11-28 14:52 ` Johannes Berg
2016-12-19 10:58 ` Lazar, Alexei Avshalom
2017-01-02 10:45 ` Johannes Berg
2017-03-06 13:54 ` Lazar, Alexei Avshalom
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=1490778081.7948.17.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ailizaro@codeaurora.org \
--cc=dcbw@redhat.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wil6210@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).