From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
"Wey-Yi Guy" <wey-yi.w.guy@intel.com>
Subject: Re: [PATCH 2/3] iwlwifi: remove STATUS_ALIVE checking from rf_kill
Date: Thu, 26 Mar 2009 18:50:08 +0100 [thread overview]
Message-ID: <200903261850.09869.helmut.schaa@gmail.com> (raw)
In-Reply-To: <1238087650-26993-3-git-send-email-reinette.chatre@intel.com>
Hi,
Am Donnerstag, 26. M=E4rz 2009 schrieb Reinette Chatre:
> From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
>=20
> Remove STATUS_ALIVE checking when HW RF KILL disabled, the bit get
> clear in __iwl_down() function; the additional checking will fail and
> cause RF can not be turn back on.
Are you sure this is needed? I'd argue we should only restart the adapt=
er
if it was alive when it got rf_killed. In case the adapter was rf_kille=
d
while the interface was down I don't think we want to restart the adapt=
er
immediately but first when the interface is taken up again.
Helmut
> Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
> ---
> drivers/net/wireless/iwlwifi/iwl-core.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>=20
> diff --git a/drivers/net/wireless/iwlwifi/iwl-core.c b/drivers/net/wi=
reless/iwlwifi/iwl-core.c
> index e1b5472..7560d6f 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-core.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-core.c
> @@ -2056,8 +2056,7 @@ void iwl_bg_rf_kill(struct work_struct *work)
> IWL_DEBUG_RF_KILL(priv,
> "HW and/or SW RF Kill no longer active, restarting "
> "device\n");
> - if (!test_bit(STATUS_EXIT_PENDING, &priv->status) &&
> - test_bit(STATUS_ALIVE, &priv->status))
> + if (!test_bit(STATUS_EXIT_PENDING, &priv->status))
> queue_work(priv->workqueue, &priv->restart);
> } else {
> /* make sure mac80211 stop sending Tx frame */
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-26 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 17:14 [PATCH 0/3] iwlwifi driver updates 03/26/2009 Reinette Chatre
2009-03-26 17:14 ` [PATCH 1/3] iwlwifi: merge and better support of suspend/resume for iwlagn and iwl3945 Reinette Chatre
2009-03-26 17:14 ` [PATCH 2/3] iwlwifi: remove STATUS_ALIVE checking from rf_kill Reinette Chatre
2009-03-26 17:14 ` [PATCH 3/3] iwl3945: use iwl_mac_conf_tx Reinette Chatre
2009-03-26 17:50 ` Helmut Schaa [this message]
2009-03-26 18:22 ` [PATCH 2/3] iwlwifi: remove STATUS_ALIVE checking from rf_kill reinette chatre
2009-03-26 19:11 ` Helmut Schaa
2009-03-26 19:30 ` reinette chatre
2009-03-26 19:49 ` Helmut Schaa
2009-03-26 20:37 ` reinette chatre
2009-03-26 20:58 ` Helmut Schaa
2009-03-26 23:26 ` reinette chatre
2009-03-27 6:19 ` Helmut Schaa
2009-03-27 6:25 ` Helmut Schaa
2009-03-27 15:45 ` reinette chatre
2009-03-27 3:49 ` reinette chatre
2009-03-27 6:18 ` Helmut Schaa
2009-03-27 16:03 ` reinette chatre
2009-03-27 16:30 ` reinette chatre
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=200903261850.09869.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=wey-yi.w.guy@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).