All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Dave <kilroyd@googlemail.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH] [try 2] orinoco: more reliable scan handling
Date: Tue, 4 Dec 2007 13:19:50 -0500	[thread overview]
Message-ID: <20071204181950.GA28285@tuxdriver.com> (raw)
In-Reply-To: <1196790166.14628.2.camel@localhost.localdomain>

On Tue, Dec 04, 2007 at 12:42:46PM -0500, Dan Williams wrote:
> On Sat, 2007-11-24 at 21:48 +0000, Dave wrote:
> > 
> > 
> > Dan Williams wrote:
> > > Bring scan result handling more in line with drivers like ipw.  Scan
> > > results are aggregated and a BSS dropped after 15 seconds if no beacon
> > > is received.  This allows the driver to interact better with userspace
> > > where more than one process may request scans or results at any time.
> > 
> > I've only seen this recently, and am using it as a basis for some other changes. However I've noticed a couple issues:
> 
> Will clean up these and submit for 2.6.25 then, thanks.

The patch is already queued in Jeff's tree.  Please send any changes
as new patches on top.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-12-04 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 16:17 [RFC PATCH] orinoco: more reliable scan handling Dan Williams
2007-10-10 18:32 ` John W. Linville
2007-10-11  3:56   ` [RFC PATCH] [try 2] " Dan Williams
     [not found]     ` <47489C2D.7030606@gmail.com>
2007-12-04 17:42       ` Dan Williams
2007-12-04 18:19         ` John W. Linville [this message]
2007-12-04 17:55       ` Dan Williams
2007-12-04 18:59         ` Dave
2007-12-04 20:19           ` 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=20071204181950.GA28285@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dcbw@redhat.com \
    --cc=kilroyd@googlemail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.