From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John W. Linville" Subject: Re: wireless: recap of current issues (actions) Date: Sat, 14 Jan 2006 19:56:17 -0500 Message-ID: <20060115005614.GB32206@tuxdriver.com> References: <20060113195723.GB16166@tuxdriver.com> <20060113212605.GD16166@tuxdriver.com> <20060113213311.GI16166@tuxdriver.com> <20060113222512.GN16166@tuxdriver.com> <43C9770F.1000400@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: To: Jeff Garzik Content-Disposition: inline In-Reply-To: <43C9770F.1000400@pobox.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Sat, Jan 14, 2006 at 05:11:27PM -0500, Jeff Garzik wrote: > John W. Linville wrote: > >Since we are toying with the issue of multiple stacks (at least in the > >wireless development kernels), some thought needs to be done w.r.t. how > >to make a final decision between the two stacks. An objective lists > >of functional feature requirements seems like a good place to start. > >IOW, I would like to have a list of features that would trigger the > >removal of one stack shortly after the other stack achieves support > >for the list. Is this feasible? > > Also, an objective and honest list of problems with both stacks should > be considered... Yes, someone (Johannes? Jiri?) had the beginnings of this a few days ago, but I seem to have lost the link. Could someone repost it? John -- John W. Linville linville@tuxdriver.com