Return-path: Received: from fg-out-1718.google.com ([72.14.220.152]:50021 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752012AbZIOM1j (ORCPT ); Tue, 15 Sep 2009 08:27:39 -0400 Received: by fg-out-1718.google.com with SMTP id 22so1251768fge.1 for ; Tue, 15 Sep 2009 05:27:42 -0700 (PDT) Message-ID: <4AAF9649.4080409@lwfinger.net> Date: Tue, 15 Sep 2009 08:27:37 -0500 From: Larry Finger MIME-Version: 1.0 To: Michael Buesch CC: "John W. Linville" , Broadcom Wireless , linux-wireless Subject: Re: [PATCH] b43: Don't abuse wl->current_dev in the led work References: <200909142322.09152.mb@bu3sch.de> <4AAECA8A.1060200@lwfinger.net> <200909151149.22565.mb@bu3sch.de> In-Reply-To: <200909151149.22565.mb@bu3sch.de> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Michael Buesch wrote: > On Tuesday 15 September 2009 00:58:18 Larry Finger wrote: >> Michael Buesch wrote: >>> Don't abuse wl->current_dev in the LED work for checking whether we're >>> going down. Add an explicit variable. >>> This fixes a crash on rmmod dereferencing the wl->current_dev NULL pointer >>> in various other places of the driver. >>> >>> Signed-off-by: Michael Buesch >> This patch does not apply. What other patches should I have beyond the >> current state of wireless-testing? > > All patches that are currently queued up. I found the ones I needed in my mailboxes. The patch cured my problem. Thanks and ack. Larry