Received: with ECARTIS (v1.0.0; list netdev); Mon, 30 Aug 2004 10:42:29 -0700 (PDT) Received: from palrel12.hp.com (palrel12.hp.com [156.153.255.237]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id i7UHgN6I004608 for ; Mon, 30 Aug 2004 10:42:24 -0700 Received: from tomil.hpl.hp.com (tomil.hpl.hp.com [15.0.152.100]) by palrel12.hp.com (Postfix) with ESMTP id 34F14407323; Mon, 30 Aug 2004 10:42:16 -0700 (PDT) Received: from bougret.hpl.hp.com (bougret.hpl.hp.com [15.4.92.227]) by tomil.hpl.hp.com (8.9.3 (PHNE_29774)/8.9.3 HPLabs Timeshare Server) with ESMTP id KAA19566; Mon, 30 Aug 2004 10:44:42 -0700 (PDT) Received: from jt by bougret.hpl.hp.com with local (Exim 3.35 #1 (Debian)) id 1C1qAZ-0008UG-00; Mon, 30 Aug 2004 10:42:15 -0700 Date: Mon, 30 Aug 2004 10:42:15 -0700 To: Jeff Garzik Cc: Jouni Malinen , netdev@oss.sgi.com, hostap@shmoo.com, Pedro Ramalhais Subject: Re: Updated WE-18 (WPA) proposal Message-ID: <20040830174215.GA32132@bougret.hpl.hp.com> Reply-To: jt@hpl.hp.com References: <20040830045441.GA7415@jm.kir.nu> <20040830165026.GD29492@bougret.hpl.hp.com> <413363CB.7060807@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <413363CB.7060807@pobox.com> User-Agent: Mutt/1.3.28i Organisation: HP Labs Palo Alto Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA. E-mail: jt@hpl.hp.com From: Jean Tourrilhes X-archive-position: 8199 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: jt@bougret.hpl.hp.com Precedence: bulk X-list: netdev Content-Length: 933 Lines: 30 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. 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. > Jeff Have fun... Jean