From: "David S. Miller" <davem@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org,
jkmaline@cc.hut.fi, james.p.ketrenos@intel.com
Subject: Re: wireless-2.6 queue opened
Date: Wed, 2 Jun 2004 21:10:38 -0700 [thread overview]
Message-ID: <20040602211038.287628ac.davem@redhat.com> (raw)
In-Reply-To: <40BE9ED8.9020505@pobox.com>
On Wed, 02 Jun 2004 23:45:28 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:
> Given that there are at least 3 complete wireless stacks (or
> thereabouts) floating about for Linux, I picked one that I felt had the
> best chance of being _evolved_ into a nice, clean, generic wireless
> stack: HostAP.
Even though I authored one of the "other" stacks, I'm totally fine
with this choice. Mainly because I simply lack the time or resources
to continue working on the stack I started.
next prev parent reply other threads:[~2004-06-03 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 3:45 wireless-2.6 queue opened Jeff Garzik
2004-06-03 4:10 ` David S. Miller [this message]
2004-06-03 4:17 ` Jeff Garzik
2004-06-04 0:12 ` James Ketrenos
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 9:13 Colin LEROY
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=20040602211038.287628ac.davem@redhat.com \
--to=davem@redhat.com \
--cc=james.p.ketrenos@intel.com \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).