From: Jiri Benc <jbenc@suse.cz>
To: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
Cc: netdev@vger.kernel.org, jkmaline@cc.hut.fi, linville@tuxdriver.com
Subject: Re: [PATCH] d80211: Take lowlevel driver's channel change time into account during scanning.
Date: Mon, 3 Jul 2006 13:58:22 +0200 [thread overview]
Message-ID: <20060703135822.123c2d9f@griffin.suse.cz> (raw)
In-Reply-To: <44A6DDC6.1040005@kpnplanet.nl>
On Sat, 01 Jul 2006 22:40:38 +0200, Gertjan van Wingerde wrote:
> Make the dscape stack take the driver-supplied channel change time into
> account when actively scanning for networks.
> This particularly has been a problem in the rt2x00 driver, where
> configuration changes are done via a work-queue, and
> the subsequent channel changes failed due to the dscape stack scheduling
> a channel update while the previous one had not
> been performed yet, resulting in failed scans.
Your mail client converts tabs to spaces. Nevertheless, I applied the
patch to my git tree.
Thanks for fixing this,
Jiri
--
Jiri Benc
SUSE Labs
prev parent reply other threads:[~2006-07-03 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 20:40 [PATCH] d80211: Take lowlevel driver's channel change time into account during scanning Gertjan van Wingerde
2006-07-03 11:58 ` Jiri Benc [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=20060703135822.123c2d9f@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=gwingerde@kpnplanet.nl \
--cc=jkmaline@cc.hut.fi \
--cc=linville@tuxdriver.com \
--cc=netdev@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).