From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: "C. McPherson" <ccmcphe@verizon.net>
Cc: mcgrof@kernel.org, lf_driver_backport@lists.linux-foundation.org,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] compat: fix system crash on 2.6.35 when flushing work
Date: Mon, 13 Aug 2012 13:15:21 +0200 [thread overview]
Message-ID: <5028E1C9.6050607@neratec.com> (raw)
In-Reply-To: <5027D79E.9050607@verizon.net>
On 08/12/2012 06:19 PM, C. McPherson wrote:
> Zefir:
> Thanks a lot for this reference. All my systems are running Ubuntu
> 10.04/10.10. I was updating our compat-wireless with the stable
> compat-wireless 3.5
> and came across this crash in our testing lab. I added your patch and
> the stable compat-wireless 3.5 is now working with our Ubuntu.
>
> -Tex
>
>
Hi Tex,
the fix Hauke provided is the correct one. The QH I posted was a lucky
punch that for some reason prevented the system crashing without
resolving the issue.
parent reply other threads:[~2012-08-13 11:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5027D79E.9050607@verizon.net>]
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=5028E1C9.6050607@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=ccmcphe@verizon.net \
--cc=lf_driver_backport@lists.linux-foundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
/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).