From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: don't power down hardware when interface is down
Date: Thu, 3 Nov 2011 18:56:24 +0200 [thread overview]
Message-ID: <4EB2C7B8.7020009@qca.qualcomm.com> (raw)
In-Reply-To: <20111103095357.10733.85983.stgit@localhost6.localdomain6>
On 11/03/2011 11:53 AM, Kalle Valo wrote:
> Jouni reported that my patch "ath6kl: power down hardware when interface
> is down" caused a regression on his x86 boxes and scan didn't work anymore.
> I was able to reproduce the problem by disabling all debug messages.
>
> So there has to be a race condition somewhere in the code and disable the
> functionality until the race is fixed. Now hardware is powered from the
> point where module is loaded until it's removed.
Applied.
Kalle
prev parent reply other threads:[~2011-11-03 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 9:53 [PATCH] ath6kl: don't power down hardware when interface is down Kalle Valo
2011-11-03 16:56 ` Kalle Valo [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=4EB2C7B8.7020009@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.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).