From: Jeff Garzik <jgarzik@pobox.com>
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: jt@hpl.hp.com, Christoph Hellwig <hch@infradead.org>,
"David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] Intersil Prism54 wireless driver
Date: Wed, 10 Mar 2004 22:02:20 -0500 [thread overview]
Message-ID: <404FD6BC.7090409@pobox.com> (raw)
In-Reply-To: <20040311024816.GC3738@jm.kir.nu>
Jouni Malinen wrote:
> I'm going to be at the IEEE 802.11 meeting for the next week which is
> probably going to take more or less all of my time, but I should be able
> to allocate more time after that. If people are interested in reviewing
> the current Host AP code from the viewpoint of what would need to happen
> before it can be merged into the kernel tree, the latest version is
> available as a snapshot from my CVS tree (pserver or tarball) at
> http://hostap.epitest.fi/. The current version is almost 20k lines, so
> there is certainly quite a bit of code to review. I hope to get this to
> about 15k lines, though, with the crypto API and backwards
> compatibility cleanup.
How about submitting a patch, when the CryptoAPI and backcompat cleanups
are complete? I will apply to the wireless-2.6 tree, and we can start
working on the kernel's overall 802.11 support from there. I don't
pretend to be an 802.11 expert, so I'll let you and Jean and other
developers drive that end of things. I'm mainly interested in keeping
the API simple and clean, and maintainable.
Jeff
next prev parent reply other threads:[~2004-03-11 3:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 2:35 [PATCH 2.6] Intersil Prism54 wireless driver Jean Tourrilhes
2004-03-04 2:37 ` Jeff Garzik
2004-03-04 2:49 ` Jean Tourrilhes
2004-03-10 3:24 ` Jean Tourrilhes
2004-03-10 7:12 ` Jeff Garzik
2004-03-10 17:21 ` Jean Tourrilhes
2004-03-10 16:55 ` Christoph Hellwig
2004-03-10 17:21 ` Jean Tourrilhes
2004-03-10 17:29 ` Christoph Hellwig
2004-03-10 17:29 ` Jeff Garzik
2004-03-10 17:52 ` Jean Tourrilhes
2004-03-10 17:58 ` Jeff Garzik
2004-03-10 23:37 ` James Ketrenos
2004-03-11 2:31 ` Jouni Malinen
2004-03-11 2:43 ` Jeff Garzik
2004-03-15 22:18 ` Pavel Machek
2004-03-15 22:44 ` Jeff Garzik
2004-03-15 22:55 ` Jean Tourrilhes
2004-03-11 2:48 ` Jouni Malinen
2004-03-11 3:02 ` Jeff Garzik [this message]
2004-03-11 3:17 ` Jouni Malinen
2004-03-11 16:28 ` Device naming for wireless NICs James Ketrenos
2004-03-11 16:36 ` Tomasz Torcz
2004-03-11 16:54 ` Matthew Galgoci
2004-03-11 18:25 ` Jeff Garzik
2004-03-11 18:23 ` Jeff Garzik
2004-03-12 10:30 ` P
2004-03-10 18:07 ` [PATCH 2.6] Intersil Prism54 wireless driver Jeff Garzik
2004-03-11 2:21 ` Jouni Malinen
2004-03-10 22:17 ` Luis R. Rodriguez
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=404FD6BC.7090409@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--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).