From: Richard Farina <sidhayn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
Hin-Tak Leung <htl10@users.sourceforge.net>,
linux-wireless@vger.kernel.org, mcgrof@gmail.com,
johannes@sipsolutions.net
Subject: Re: [PATCH] rtl8187: Fix kernel oops when device is removed when LEDS enabled (Bugzilla #14539)
Date: Wed, 04 Nov 2009 23:57:55 -0500 [thread overview]
Message-ID: <4AF25B53.3090204@gmail.com> (raw)
In-Reply-To: <20091104184700.GK12965@tuxdriver.com>
John W. Linville wrote:
> On Wed, Nov 04, 2009 at 12:13:02PM -0600, Larry Finger wrote:
>
>> On 11/04/2009 10:54 AM, John W. Linville wrote:
>>
>>> On Wed, Nov 04, 2009 at 09:54:37AM -0600, Larry Finger wrote:
>>>
>>>
>>>> I will try once more to get netconsole working to capture the backtrace.
>>>>
>>> No need, I think I understand it now. The new order still sorta
>>> looks/feels "wrong", but it seems fine. Maybe an alternative would
>>> be to make the brightness_set routine aware of the shutdown and not
>>> queue the work? Maybe even ieee80211_queue_delayed_work could be
>>> made a bit smarter here?
>>>
>> Are either of these questions a request, or are they musings?
>>
>
> They are musings -- but feel free to be inspired! :-)
>
>
I can't speak for "proper coding style" or "preferred fixes" or whatever
you awesome coders call things, but I can say that myself and a few
others have extensively test _this_ fix and can no longer crash the
kernel. As the original reporter I am more than satisfied that this is
fixed. Just my 0.02$
Thanks,
Rick Farina
next prev parent reply other threads:[~2009-11-05 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 6:00 [PATCH] rtl8187: Fix kernel oops when device is removed when LEDS enabled (Bugzilla #14539) Larry Finger
2009-11-04 15:11 ` John W. Linville
2009-11-04 15:30 ` Christian Lamparter
2009-11-04 16:49 ` John W. Linville
2009-11-05 0:14 ` Herton Ronaldo Krzesinski
2009-11-05 2:34 ` Larry Finger
2009-11-05 4:55 ` Richard Farina
2009-11-05 5:16 ` Larry Finger
2009-11-04 15:54 ` Larry Finger
2009-11-04 16:54 ` John W. Linville
2009-11-04 18:13 ` Larry Finger
2009-11-04 18:47 ` John W. Linville
2009-11-05 4:57 ` Richard Farina [this message]
2009-11-05 6:00 ` Larry Finger
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=4AF25B53.3090204@gmail.com \
--to=sidhayn@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=htl10@users.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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).