netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mcgrof@studorgs.rutgers.edu (Luis R. Rodriguez)
To: Netdev <netdev@oss.sgi.com>
Subject: Re: HostAP:  alive or dead?
Date: Thu, 27 May 2004 15:12:47 -0400	[thread overview]
Message-ID: <20040527191247.GS3330@ruslug.rutgers.edu> (raw)
In-Reply-To: <40B62FD3.8040601@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

On Thu, May 27, 2004 at 02:13:39PM -0400, Jeff Garzik wrote:
> 
> I've been wanting to merge it, and starting working on the generic 
> wireless layer, for a while now.

Hey Jeff,

can you elaborate on the wireless layer bit?

	Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-27 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 18:13 HostAP: alive or dead? Jeff Garzik
2004-05-27 19:12 ` Luis R. Rodriguez [this message]
2004-05-29  1:49 ` Jouni Malinen

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=20040527191247.GS3330@ruslug.rutgers.edu \
    --to=mcgrof@studorgs.rutgers.edu \
    --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).