From: Zhu Yi <yi.zhu@intel.com>
To: Tomas Winkler <tomas.winkler@intel.com>, greg@kroah.com
Cc: "stable@kernel.org" <stable@kernel.org>,
"rjw@sisk.pl" <rjw@sisk.pl>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] iwlwifi: fix suspend to RAM in iwlwifi
Date: Mon, 10 Nov 2008 09:26:16 +0800 [thread overview]
Message-ID: <1226280376.2604.280.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1226191867-22324-3-git-send-email-tomas.winkler@intel.com>
On Sun, 2008-11-09 at 08:51 +0800, Tomas Winkler wrote:
> This patch fixes suspend to RAM after by moving
> notify_mac out of iwlwifi mutex
>
> http://bugzilla.kernel.org/show_bug.cgi?id=11845
Greg, please also merge the iwl3945 counterpart for this problem.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d54bc4e3fc5c56600a13c9ebc0a7e1077ac05d59
Thanks,
-yi
> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> Tested-by: Carlos R. Mafra <crmafra2@gmail.com>
> Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Rafael J. Wysocki <rjw@sisk.pl>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> drivers/net/wireless/iwlwifi/iwl-agn.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/iwlwifi/iwl-agn.c b/drivers/net/wireless/iwlwifi/iwl-agn.c
> index e01f048..edab202 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-agn.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-agn.c
> @@ -2090,7 +2090,6 @@ static void iwl_alive_start(struct iwl_priv *priv)
> iwl4965_error_recovery(priv);
>
> iwl_power_update_mode(priv, 1);
> - ieee80211_notify_mac(priv->hw, IEEE80211_NOTIFY_RE_ASSOC);
>
> if (test_and_clear_bit(STATUS_MODE_PENDING, &priv->status))
> iwl4965_set_mode(priv, priv->iw_mode);
> @@ -2342,6 +2341,7 @@ static void iwl_bg_alive_start(struct work_struct *data)
> mutex_lock(&priv->mutex);
> iwl_alive_start(priv);
> mutex_unlock(&priv->mutex);
> + ieee80211_notify_mac(priv->hw, IEEE80211_NOTIFY_RE_ASSOC);
> }
>
> static void iwl4965_bg_rf_kill(struct work_struct *work)
next prev parent reply other threads:[~2008-11-10 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 0:51 [PATCH 0/2] iwlwifi fixes for stable 2.6.27 Tomas Winkler
2008-11-09 0:51 ` [PATCH 1/2] iwlwifi: generic init calibrations framework Tomas Winkler
2008-11-09 0:51 ` [PATCH 2/2] iwlwifi: fix suspend to RAM in iwlwifi Tomas Winkler
2008-11-10 1:26 ` Zhu Yi [this message]
2008-11-11 20:04 ` [stable] " Greg KH
2008-11-09 4:18 ` [stable] [PATCH 0/2] iwlwifi fixes for stable 2.6.27 Greg KH
2008-11-09 7:13 ` Tomas Winkler
2008-11-11 20:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-11-09 0:46 Tomas Winkler
2008-11-09 0:46 ` [PATCH 1/2] iwlwifi: generic init calibrations framework Tomas Winkler
2008-11-09 0:46 ` [PATCH 2/2] iwlwifi: fix suspend to RAM in iwlwifi Tomas Winkler
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=1226280376.2604.280.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=tomas.winkler@intel.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).