From: abuas_z <rocky7@wp.pl>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Pavel Roskin <proski@gnu.org>,
Orinoco Development List <orinoco-devel@lists.sourceforge.net>,
<netdev@oss.sgi.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Orinoco-devel] [0/5] Orinoco merge updates, part the fourth
Date: Wed, 30 Mar 2005 09:56:19 +0200 [thread overview]
Message-ID: <548301398.20050330095619@wp.pl> (raw)
In-Reply-To: <20050330034238.GF6478@localhost.localdomain>
Hello,
DG> Here's yet another batch of orinoco updates.
Will this patches be included in CVS-Head code? Now I checked and the
last modification of orinoco.c was about 4 days ago, when switch to
enable monitor mode on all firmwares was included...
DG> Smaller and less significant than the last,
What was the last?
DG> this is basically a handful of remaining small updates before
DG> tackling the big changes (wext v15, monitor and scanning).
So, the next thing that will be do, will be WPA and monitor mode
improvement (maybe in all firmwares)?
--
Bye,
abuas_z mailto:rocky7@wp.pl
The Bat! v3.0.2.10, Windows XP 5.1, Build 2600, Service Pack 1
prev parent reply other threads:[~2005-03-30 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 3:42 [0/5] Orinoco merge updates, part the fourth David Gibson
2005-03-30 3:43 ` [1/5] Orinoco merge updates, part the fourth: wireless stats updates David Gibson
2005-03-30 3:44 ` [2/5] Orinoco merge updates, part the fourth: ignore_disconnect flag David Gibson
2005-03-30 3:44 ` [3/5] Orinoco merge updates, part the fourth: kill dump_recs David Gibson
2005-03-30 3:44 ` [4/5] Orinoco merge updates, part the fourth: don't set channel in managed mode David Gibson
2005-03-30 3:45 ` [5/5] Orinoco merge updates, part the fourth: consolidate allocation code David Gibson
2005-03-31 0:48 ` [1/5] Orinoco merge updates, part the fourth: wireless stats updates Jeff Garzik
2005-03-30 7:56 ` abuas_z [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=548301398.20050330095619@wp.pl \
--to=rocky7@wp.pl \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=orinoco-devel@lists.sourceforge.net \
--cc=proski@gnu.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.