From: "John W. Linville" <linville@tuxdriver.com>
To: Ken Lewis <kennylewis@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org, linux-wireless@vger.kernel.org,
davem@davemloft.net, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Regression: 2.6.30-rc5 and rt2x00 / rt2500pci
Date: Mon, 18 May 2009 09:11:45 -0400 [thread overview]
Message-ID: <20090518131145.GB2814@tuxdriver.com> (raw)
In-Reply-To: <5a44caba0905170838l2876df90q200f9a8b6411f7ce@mail.gmail.com>
On Sun, May 17, 2009 at 04:38:58PM +0100, Ken Lewis wrote:
> 2009/5/15 John W. Linville <linville@tuxdriver.com>:
> > On Fri, May 15, 2009 at 03:40:44PM +0100, Ken Lewis wrote:
> >> I've been looking for a bug in Linux-Next that makes my rt2500pci
> >> wireless card unusable. ...
> >
> > Please apply this patch:
> >
> > http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/0002-mac80211-avoid-NULL-ptr-deref-when-finding-max_rate.patch
> >
> > A pull request was sent to Dave M. a couple of days ago. I imagine
> > that it will make its way to Linus shortly.
>
> Thank you, John. The patch makes 2.6.30-rc5 work for me -- no more bug
> dump and the wireless card works fine.
>
> I'm about to try and see if it *also* makes rt2x00 work when applied
> against the linux-next tree (and next-20090515 in particular).
I'm guessing it didn't help with this part, since -next should have
already had the patch...?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-05-18 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 14:40 Regression: 2.6.30-rc5 and rt2x00 / rt2500pci Ken Lewis
2009-05-15 14:46 ` John W. Linville
2009-05-17 15:38 ` Ken Lewis
2009-05-18 13:11 ` John W. Linville [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=20090518131145.GB2814@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=kennylewis@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.