From: "Tomas Winkler" <tomasw@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2008-08-22
Date: Mon, 25 Aug 2008 22:33:00 +0300 [thread overview]
Message-ID: <1ba2fa240808251233n214048c7ife265c473331d618@mail.gmail.com> (raw)
In-Reply-To: <20080825184921.GA17297@tuxdriver.com>
On Mon, Aug 25, 2008 at 9:49 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Sat, Aug 23, 2008 at 04:21:23AM +0300, Tomas Winkler wrote:
>> On Sat, Aug 23, 2008 at 2:46 AM, John W. Linville
>> <linville@tuxdriver.com> wrote:
>> > Dave,
>> >
>> > Here is my current stack of updates for 2.6.28 -- included is an
>> > orinoco update to support WPA on certain firmware, the new libertas_tf
>> > driver, a number of cleanups, and a variety of other driver updates.
>> > Still more to come, but I think it is better to get these out rather
>> > than wait for the rest...
>> >
>> > Please let me know of there are problems!
>> >
>>
>> Missing this one
>> iwlwifi: allow consecutive scans in unassociated state
>> http://marc.info/?l=linux-wireless&m=121919791411147&w=2
>> Thanks
>> Tomas
>
> Hence the phrase "Still more to come"...
>
Sure, this was just integral part of the direct probe/association
fixes included in this bulk
Tomas
next prev parent reply other threads:[~2008-08-25 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 23:46 pull request: wireless-next-2.6 2008-08-22 John W. Linville
2008-08-23 1:21 ` Tomas Winkler
2008-08-25 18:49 ` John W. Linville
2008-08-25 19:33 ` Tomas Winkler [this message]
2008-08-23 12:08 ` David Miller
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=1ba2fa240808251233n214048c7ife265c473331d618@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--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