linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iwlwifi: change WARN_ON to IWL_WARN in iwl_mac_add_interface
Date: Thu, 30 Sep 2010 16:52:07 -0700	[thread overview]
Message-ID: <1285890728.12056.50.camel@wwguy-huron> (raw)
In-Reply-To: <20100930142734.GA2368@redhat.com>

On Thu, 2010-09-30 at 07:27 -0700, Stanislaw Gruszka wrote:
> We can start restarting firmware or RF kill switch can be turned on
> during call to iwl_mac_add_interface(). That are normal working
> conditions, so do not print call trace, just print simple message
> instead.
> 
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> ---
>  drivers/net/wireless/iwlwifi/iwl-core.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/net/wireless/iwlwifi/iwl-core.c b/drivers/net/wireless/iwlwifi/iwl-core.c
> index 5c56893..b7adcf8 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-core.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-core.c
> @@ -2003,7 +2003,8 @@ int iwl_mac_add_interface(struct ieee80211_hw *hw, struct ieee80211_vif *vif)
>  
>  	mutex_lock(&priv->mutex);
>  
> -	if (WARN_ON(!iwl_is_ready_rf(priv))) {
> +	if (!iwl_is_ready_rf(priv)) {
> +		IWL_WARN(priv, "Try to add interface when device not ready\n");
>  		err = -EINVAL;
>  		goto out;
>  	}



      reply	other threads:[~2010-09-30 23:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 14:27 [PATCH] iwlwifi: change WARN_ON to IWL_WARN in iwl_mac_add_interface Stanislaw Gruszka
2010-09-30 23:52 ` Guy, Wey-Yi [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=1285890728.12056.50.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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).