From: Holger Schurig <holgerschurig@gmail.com>
To: linux-wireless@vger.kernel.org, Samuel Ortiz <samuel@sortiz.org>
Cc: Holger Schurig <holgerschurig@googlemail.com>,
John Linville <linville@tuxdriver.com>,
Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH 10/10] [RFC, v4] libertas: cfg80211 support
Date: Tue, 26 Jan 2010 14:20:23 +0100 [thread overview]
Message-ID: <201001261420.23936.holgerschurig@gmail.com> (raw)
In-Reply-To: <1264432854.2250.17.camel@caravaggio>
> > + /* stop network while we're away from our main channel */
> > + running = !netif_queue_stopped(priv->dev);
> > + carrier = netif_carrier_ok(priv->dev);
> > + if (running)
> > + netif_stop_queue(priv->dev);
> > + if (carrier)
> > + netif_carrier_off(priv->dev);
> Stopping the tx queue is fine, but turning the carrier signal
off is
> not.
The patch is a bit older, then the wext-libertas did the same
thing. In the meantime, the wext-libertas doesn't mangle the
carrier anymore, and thus cfg80211-libertas shouldn't do it
either.
> A couple of questions here:
> - What is this 50ms delay for ?
Good question. A crude way to combine two "almost concurrent"
scan requests into one. However, if that was the intention, it
should have gotten a comment. You can try to delete the delay.
> - Why dont you set the scan_request pointer prior to scheduling
> the scanning work ?
Hehe, because I can. After all, there's a delay in my patch :-)
If you rewrite this: the idea was that priv->scan_req not only
contains the details for this scan (e.g. which channels,
active/passive), but also implicitly if currently a scan is
underway.
BTW: thanks for this quick review.
> Again, I think this should make it to wireless-testing soon so
> that people can start using it.
Currently, wext-libertas still supports more options than
cfg80211-libertas. That did hold me. However, feel free to grab
my RFC-patch and continue, that's the reason I added
a "Signed-off-by:"-line.
Oh, and please. you the delete-line or delete-block function of
your e-mail client liberately. No reason to quote 2000 lines
when you just write 20 lines or so ...
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2010-01-26 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 14:25 [PATCH 00/10] [PATCH] libertas: remove WEXT, add CFG80211 Holger Schurig
2009-12-02 14:25 ` [PATCH 01/10] libertas: use priv->mesh_tlv instead of priv->mesh_fw_ver Holger Schurig
2009-12-02 14:25 ` [PATCH 02/10] libertas: remove mesh_autostart_enabled and sync_channel Holger Schurig
2009-12-02 14:25 ` [PATCH 03/10] libertas: move mesh-related definitions into mesh.h Holger Schurig
2009-12-02 14:25 ` [PATCH 04/10] libertas: decouple mesh and rtap Holger Schurig
2009-12-02 14:26 ` [PATCH 05/10] libertas: move mesh SSID initialization into mesh.c Holger Schurig
2009-12-02 14:26 ` [PATCH 06/10] libertas: add access functions for mesh open/connect status Holger Schurig
2009-12-02 14:26 ` [PATCH 07/10] libertas: make mesh configurable Holger Schurig
2009-12-02 14:26 ` [PATCH 08/10] libertas: remove priv->capability Holger Schurig
2009-12-02 14:26 ` [PATCH 09/10] libertas: remove priv->ratebitmap Holger Schurig
2009-12-02 14:26 ` [PATCH 10/10] [RFC, v4] libertas: cfg80211 support Holger Schurig
2010-01-25 15:20 ` Samuel Ortiz
2010-01-26 13:20 ` Holger Schurig [this message]
2009-12-02 20:45 ` [PATCH 00/10] [PATCH] libertas: remove WEXT, add CFG80211 Dan Williams
2009-12-03 10:02 ` Holger Schurig
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=201001261420.23936.holgerschurig@gmail.com \
--to=holgerschurig@gmail.com \
--cc=dcbw@redhat.com \
--cc=holgerschurig@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=samuel@sortiz.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).