From: Kalle Valo <kalle.valo@nokia.com>
To: "Zhu Yi" <yi.zhu@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: 2.6.28-rc2-wl: network lockups with iwl3945
Date: Mon, 03 Nov 2008 09:44:48 +0200 [thread overview]
Message-ID: <87hc6pb6dr.fsf@nokia.com> (raw)
In-Reply-To: <1225698103.2917.312.camel@debian.sh.intel.com> (ext Zhu Yi's message of "Mon\, 03 Nov 2008 15\:41\:43 +0800")
Zhu Yi <yi.zhu@intel.com> writes:
> On Mon, 2008-11-03 at 15:26 +0800, Johannes Berg wrote:
>> I think this has been fixed for iwlagn recently, but I guess iwl3945
>> will always be forgotten ;)
>
> Yup. Please try attached patch.
Thanks! I'm travelling today, but I try to find some free time and an
open AP to test this :)
--
Kalle Valo
next prev parent reply other threads:[~2008-11-03 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 8:22 2.6.28-rc2-wl: network lockups Kalle Valo
2008-11-02 20:23 ` 2.6.28-rc2-wl: network lockups with iwl3945 Kalle Valo
2008-11-03 7:26 ` Johannes Berg
2008-11-03 7:41 ` Zhu Yi
2008-11-03 7:44 ` Kalle Valo [this message]
2008-11-04 7:21 ` Kalle Valo
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=87hc6pb6dr.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).