From: Marcel Holtmann <holtmann@linux.intel.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 21:09:01 +0200 [thread overview]
Message-ID: <1222369742.6442.0.camel@californication> (raw)
In-Reply-To: <20080925114133.GA5044@tuxdriver.com>
Hi John,
> > > 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 was hitting this one a frequent basis on a 64-bit Linux running on an
off-the-shelf X61.
Regards
Marcel
prev parent reply other threads:[~2008-09-25 19:09 UTC|newest]
Thread overview: 9+ 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:22 ` David Miller
2008-09-25 5:47 ` Zhu Yi
[not found] ` <1222321622.2510.455.camel-F7Q/YMNgnyhhZnBKgDE8z0EOCMrvLtNR@public.gmane.org>
2008-09-25 11:41 ` John W. Linville
2008-09-25 12:27 ` Johannes Berg
[not found] ` <20080925114133.GA5044-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-09-25 14:57 ` Tomas Winkler
[not found] ` <1ba2fa240809250757x32aa450k523d71e555c221e4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-25 15:47 ` John W. Linville
2008-09-25 15:52 ` Tomas Winkler
2008-09-25 19:09 ` Marcel Holtmann [this message]
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=1222369742.6442.0.camel@californication \
--to=holtmann@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).