linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH, take 2] libertas: implement SSID scanning for SIOCSIWSCAN
Date: Wed, 27 Feb 2008 21:28:37 -0500	[thread overview]
Message-ID: <1204165717.26788.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200802261522.05676.hs4233@mail.mn-solutions.de>

On Tue, 2008-02-26 at 15:22 +0100, Holger Schurig wrote:
> libertas: implement SSID scanning for SIOCSIWSCAN
> 
> After my bit scan re-writing the SIOCSIWSCAN wext ioctl no longer supported
> scanning for a specific SSID. However, wpa_supplicant is a possible user of
> this ioctl, so here is code that add's this.
> 
> While passing, removed even more of the debugfs-based scanning. You can (and
> should) the SIOCSIWSCAN to ask for scans, so there is no need for
> proprietary interfaces for scanning. And, besides, the scan result couldn't
> be used further, e.g. not for associating.

Was going to test this; but it doesn't apply to either libertas-2.6 or
to wireless-2.6/everything.  Which branch is it a diff from?

Also, should we still be targeting libertas-2.6 or just go straight to
Linville since Woodhouse seems to have gone quiet for a bit?  If he has,
we should probably get Linville to pull the latest from libertas-2.6
since there's a few good cleanups in there (the should_deauth_infra()
return value for one).  Then send further patches to wireless-2.6 until
woodhouse shows up again.

Dan



  parent reply	other threads:[~2008-02-28  2:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 14:22 [PATCH, take 2] libertas: implement SSID scanning for SIOCSIWSCAN Holger Schurig
2008-02-26 15:44 ` Marc Pignat
2008-02-28  2:28 ` Dan Williams [this message]
2008-02-28  6:35   ` Holger Schurig
2008-02-28 14:05     ` John W. Linville
2008-03-03 19:18 ` Dan Williams
2008-03-04  6:38   ` Holger Schurig
2008-03-04 14:04     ` Dan Williams
2008-03-04 19:38 ` Dan Williams

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=1204165717.26788.1.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).