From: "Tomas Winkler" <tomasw@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Zhu Yi" <yi.zhu@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pull request: wireless-2.6 2008-09-24
Date: Thu, 25 Sep 2008 18:52:39 +0300 [thread overview]
Message-ID: <1ba2fa240809250852k62266473o7a8ac858c587213d@mail.gmail.com> (raw)
In-Reply-To: <20080925154753.GA3277@tuxdriver.com>
On Thu, Sep 25, 2008 at 6:47 PM, John W. Linville
<linville@tuxdriver.com> 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
>> <linville@tuxdriver.com> 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
next prev parent reply other threads:[~2008-09-25 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 23:17 pull request: wireless-2.6 2008-09-24 John W. Linville
2008-09-24 23:17 ` John W. Linville
2008-09-24 23:22 ` David Miller
2008-09-25 5:47 ` Zhu Yi
2008-09-25 11:41 ` John W. Linville
2008-09-25 11:41 ` John W. Linville
2008-09-25 12:27 ` Johannes Berg
2008-09-25 14:57 ` Tomas Winkler
2008-09-25 14:57 ` Tomas Winkler
2008-09-25 15:47 ` John W. Linville
2008-09-25 15:47 ` John W. Linville
2008-09-25 15:52 ` Tomas Winkler [this message]
2008-09-25 19:09 ` Marcel Holtmann
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=1ba2fa240809250852k62266473o7a8ac858c587213d@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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 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.