From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: netdev@vger.kernel.org, Michael Wu <flamingice@sourmilk.net>,
Jouni Malinen <jkmaline@cc.hut.fi>,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [PATCH wireless-2.6] add adm8211 wireless driver
Date: Mon, 24 Apr 2006 17:13:45 -0400 [thread overview]
Message-ID: <20060424211340.GE21761@tuxdriver.com> (raw)
In-Reply-To: <444026BF.2080801@gmail.com>
On Fri, Apr 14, 2006 at 06:48:31PM -0400, Luis R. Rodriguez wrote:
>
> John, (Jean please update your docs)
>
> as promised here's a new 802.11b driver for wireless-2.6. It is based on
> Jouni Malinen's original work and maintained by Michael Wu.
> This driver is for ADM8211A, ADM8211B, and ADM8211C based cards which
> are PCI/mini-PCI/Cardbus 802.11b cards. This driver has been tested and
> known to work with the following wireless cards:
Applied to master branch of wireless-2.6. Let's get this one properly
reviewed and whipped into shape in time for 2.6.18!
John
--
John W. Linville
linville@tuxdriver.com
parent reply other threads:[~2006-04-24 21:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <444026BF.2080801@gmail.com>]
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=20060424211340.GE21761@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=flamingice@sourmilk.net \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--cc=mcgrof@gmail.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 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.