From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH] cfg80211: don't optimise wext calls too much
Date: Fri, 17 Jul 2009 13:50:14 +0300 [thread overview]
Message-ID: <87vdlrpord.fsf@litku.valot.fi> (raw)
In-Reply-To: <1247737144.24433.11.camel@johannes.local> (Johannes Berg's message of "Thu\, 16 Jul 2009 11\:39\:04 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> In the wext code I tried to not reconnect all the time
> when the user wasn't really sure what they were doing,
> like setting the BSSID back to the same value it was.
> However, this optimisation should only be done while
> associated so that setting the BSSID back to the same
> value that it was actually triggers a new association
> if not currently associated. To achieve, that, put the
> relevant code into the !IDLE case instead.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
At least this patch cured my resume problems I reported earlier[1]. It
will take few days to test the dropping from network case, but I'm sure
this patch will help with that problem as well. If not, I'll report
about the issue. Thanks for fixing this.
Tested-by: Kalle Valo <kalle.valo@iki.fi>
[1] http://www.spinics.net/lists/linux-wireless/msg35797.html
--
Kalle Valo
next prev parent reply other threads:[~2009-07-17 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 9:39 [PATCH] cfg80211: don't optimise wext calls too much Johannes Berg
2009-07-17 10:50 ` Kalle Valo [this message]
2009-07-18 12:00 ` Marcel Holtmann
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=87vdlrpord.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.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).