|To:||Jouni Malinen <jkmaline@xxxxxxxxx>|
|Subject:||Re: [PATCH 2.6] Intersil Prism54 wireless driver|
|From:||Jeff Garzik <jgarzik@xxxxxxxxx>|
|Date:||Wed, 10 Mar 2004 21:43:08 -0500|
|Cc:||James Ketrenos <jketreno@xxxxxxxxxxxxxxxxxx>, jt@xxxxxxxxxx, Christoph Hellwig <hch@xxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx, Linux kernel mailing list <linux-kernel@xxxxxxxxxxxxxxx>|
|References:||<20040304023524.GA19453@bougret.hpl.hp.com> <20040310165548.A24693@infradead.org> <20040310172114.GA8867@bougret.hpl.hp.com> <404F5097.firstname.lastname@example.org> <20040310175200.GA9531@bougret.hpl.hp.com> <404F5744.email@example.com> <404FA6AC.firstname.lastname@example.org> <20040311023141.GB3738@jm.kir.nu>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703|
Jouni Malinen wrote:
done, I would hope to get the code merged into the kernel tree either with full Host AP driver or separately. One option would be to first add Host AP driver in its current structure (i.e., everything in drivers/net/wireless) and then create a new directory (net/ieee80211 ?) for generic IEEE 802.11 functionality and start moving things like the IEEE 802.11 encryption into the new location.
Given the discussion today, I think my preference is to merge all of HostAP into the wireless-2.6 tree I just created, then submit patches to that which create and populate net/802_11. Once the work on that is mostly done, it can get merged back into the main upstream tree.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH 2.6] Intersil Prism54 wireless driver, Jouni Malinen|
|Next by Date:||Re: [PATCH 2.6] Intersil Prism54 wireless driver, Jouni Malinen|
|Previous by Thread:||Re: [PATCH 2.6] Intersil Prism54 wireless driver, Jouni Malinen|
|Next by Thread:||Re: [PATCH 2.6] Intersil Prism54 wireless driver, Pavel Machek|
|Indexes:||[Date] [Thread] [Top] [All Lists]|