From: Johannes Berg <johannes@sipsolutions.net>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [WEXT]: multiple calls for SIOCGIWSTATS return same value
Date: Wed, 10 Jun 2015 08:12:15 +0200 [thread overview]
Message-ID: <1433916735.1921.2.camel@sipsolutions.net> (raw)
In-Reply-To: <20150609202558.208609e7@erg.abdn.ac.uk>
On Tue, 2015-06-09 at 20:25 -0600, Gerrit Renker wrote:
> Many thanks for providing the patch. I just tried it and it fixed both problems
> (access point signal level/quality and signal level reported for BSSes in scan
> result). Not sure if trace results are still needed, but I can do that if needed.
No, I did the tracing myself - it showed strange behaviour that
eventually helped me pinpoint the problem :)
johannes
prev parent reply other threads:[~2015-06-10 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 2:37 [WEXT]: multiple calls for SIOCGIWSTATS return same value Gerrit Renker
2015-06-08 7:18 ` Johannes Berg
2015-06-09 1:58 ` Gerrit Renker
2015-06-09 7:33 ` Johannes Berg
2015-06-10 2:25 ` Gerrit Renker
2015-06-10 6:12 ` Johannes Berg [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=1433916735.1921.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gerrit@erg.abdn.ac.uk \
--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).