From: Pavel Machek <pavel@ucw.cz>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jouni Malinen <jkmaline@cc.hut.fi>,
James Ketrenos <jketreno@linux.co.intel.com>,
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: Mon, 15 Mar 2004 23:18:26 +0100 [thread overview]
Message-ID: <20040315221826.GA305@elf.ucw.cz> (raw)
In-Reply-To: <404FD23C.4020205@pobox.com>
On St 10-03-04 21:43:08, Jeff Garzik wrote:
> 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.
Can we have net/wifi? 802_11 looks ugly. 802.11 would be better, but
wifi seems best.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-15 22:18 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 [this message]
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
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=20040315221826.GA305@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.co.intel.com \
--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).