Return-path: Received: from fk-out-0910.google.com ([209.85.128.185]:37163 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752868AbYIYPwl (ORCPT ); Thu, 25 Sep 2008 11:52:41 -0400 Received: by fk-out-0910.google.com with SMTP id 18so471205fkq.5 for ; Thu, 25 Sep 2008 08:52:39 -0700 (PDT) Message-ID: <1ba2fa240809250852k62266473o7a8ac858c587213d@mail.gmail.com> (sfid-20080925_175246_364807_02B7213E) Date: Thu, 25 Sep 2008 18:52:39 +0300 From: "Tomas Winkler" To: "John W. Linville" Subject: Re: pull request: wireless-2.6 2008-09-24 Cc: "Zhu Yi" , "davem@davemloft.net" , "linux-wireless@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" In-Reply-To: <20080925154753.GA3277@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <20080924231720.GD3639@tuxdriver.com> <1222321622.2510.455.camel@debian.sh.intel.com> <20080925114133.GA5044@tuxdriver.com> <1ba2fa240809250757x32aa450k523d71e555c221e4@mail.gmail.com> <20080925154753.GA3277@tuxdriver.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Sep 25, 2008 at 6:47 PM, John W. Linville wrote: > On Thu, Sep 25, 2008 at 05:57:33PM +0300, Tomas Winkler wrote: >> On Thu, Sep 25, 2008 at 2:41 PM, John W. Linville >> wrote: >> > On Thu, Sep 25, 2008 at 01:47:02PM +0800, Zhu Yi wrote: >> >> On Wed, 2008-09-24 at 17:17 -0600, John W. Linville wrote: >> >> > Dave, >> >> > >> >> > One more for 2.6.27 -- a fix for a possible interrupt storm. There is >> >> > even a link in the commit log to a youtube video of the storm in >> >> > progress. :-) >> >> > >> >> > Let me know if there are problems! >> >> >> >> Can you also add this one? It doesn't panic the kernel when a frame from >> >> firmware is invalid. >> >> >> >> http://marc.info/?l=linux-wireless&m=122219037706528&w=2 >> > >> > Is there an open bug report for that anywhere? Is this something >> > that real users (no offense to Johannes) are likely to hit? >> >> I'm just exporting the major bugs from our internal database to >> buzilla, 5000 is new so >> we are hitting the problems during testing before users report them. >> >> Now I don't know if it was good idea to push the driver upstream same >> time as it hits the market. > > You're right -- pushing it sooner rather than sitting on it internally > probably would have helped to give it more visibility sooner. I think it was pushed on time it would not bring the fixes sooner. But we are getting again to the same arguments Tomas