From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Jouni Malinen <jkmaline@cc.hut.fi>,
netdev@oss.sgi.com, hostap@shmoo.com,
Pedro Ramalhais <ramalhais@serrado.net>
Subject: Re: Updated WE-18 (WPA) proposal
Date: Mon, 30 Aug 2004 13:55:52 -0400 [thread overview]
Message-ID: <41336A28.9010608@pobox.com> (raw)
In-Reply-To: <20040830174215.GA32132@bougret.hpl.hp.com>
Jean Tourrilhes wrote:
> On Mon, Aug 30, 2004 at 01:28:43PM -0400, Jeff Garzik wrote:
>
>>Jean Tourrilhes wrote:
>>
>>> Don't worry, I'll fix that. Anyway, WE-17 is pending in Jeff's
>>>tree, and I don't think he will make major changes to it.
>>
>>
>>hehe :)
>>
>>Yep, it's merged in netdev-2.6 (and thus -mm as well), and queued for
>>upstream.
>
>
> Thanks ;-)
>
>
>>FWIW any 'radical' wireless changes will go into wireless-2.6. There is
>>still the stable upstream branch, to which WE patches can continue to be
>>applied...
>
>
> If you don't mind, I would like a bit more understanding about
> how much is "radical" and how much is not. I would personally put that
> around "breaking backward compatibility", but you may have other
> ideas.
Yes, as discussed (er, argued :)) radical would include breaking
backwards compat.
> Also, I'm not clear how the stuff in wireless-2.6 is supposed
> to trickle into the other trees (netdev-2.6, -mm and Linus's), and how
> to better link it with the CVS of the various drivers involved.
Less of a trickle than a flood: wireless-2.6 should be the target for
development of shared wireless stack code. As several drivers are
currently using bits of HostAP, for example, wireless-2.6 should be a
focal point for patches that modify these drivers to instead share the
same code.
Once this generic work is done, it would get pushed all at once to
netdev-2.6, where it would receive testing in -mm. Then, later, pushed
to mainline.
Jeff
next prev parent reply other threads:[~2004-08-30 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 4:54 Updated WE-18 (WPA) proposal Jouni Malinen
2004-08-30 16:50 ` Jean Tourrilhes
2004-08-30 17:28 ` Jeff Garzik
2004-08-30 17:42 ` Jean Tourrilhes
2004-08-30 17:55 ` Jeff Garzik [this message]
2004-08-30 22:01 ` Luis R. Rodriguez
2004-08-30 22:20 ` Jeff Garzik
2004-08-31 8:54 ` Luis R. Rodriguez
2004-08-31 15:33 ` Pedro Ramalhais
2004-08-31 15:48 ` Vladimir Kondratiev
2004-08-31 21:04 ` Luis R. Rodriguez
2004-08-31 0:49 ` Pedro Ramalhais
2004-08-31 1:30 ` 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=41336A28.9010608@pobox.com \
--to=jgarzik@pobox.com \
--cc=hostap@shmoo.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
--cc=ramalhais@serrado.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.