From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "alban.gruin@gmail.com" <alban.gruin@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: [PATCH] iwlwifi: mvm: fix usage of debug specific variables
Date: Wed, 4 Mar 2015 18:25:51 +0000 [thread overview]
Message-ID: <1425493551.2820.5.camel@egrumbacBox> (raw)
In-Reply-To: <871tl4ej9w.fsf@ylate.i-did-not-set--mail-host-address--so-tickle-me>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3128 bytes --]
Hi,
On Wed, 2015-03-04 at 18:59 +0100, Alban Gruin wrote:
> Some variables in structs "iwl_mvm" and "iwl_mvm_vif" are used for debug
> purpose, and are declared only if CONFIG_IWLWIFI_DEBUGFS is
> set. However, some of these variables are used even if
> CONFIG_IWLWIFI_DEBUGFS is not set, resulting in a compilation error.
> This patch aims to fix this issue by adding a preprocessor condition
> where these variables are used.
>
oh well... thanks for the heads up.
Your patch is not perfect, but I'll fix the problems in our internal
tree and the fix will be pushed out soon.
Thanks!
> Signed-off-by: Alban Gruin <alban.gruin@gmail.com>
> ---
> drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c | 4 ++++
> drivers/net/wireless/iwlwifi/mvm/phy-ctxt.c | 3 +++
> 2 files changed, 7 insertions(+)
> diff --git a/drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c b/drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c
> index 581b3b8..42bd545 100644
> --- a/drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c
> +++ b/drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c
> @@ -1375,10 +1375,12 @@ static void iwl_mvm_beacon_loss_iterator(void *_data, u8 *mac,
> {
> struct iwl_missed_beacons_notif *missed_beacons = _data;
> struct iwl_mvm_vif *mvmvif = iwl_mvm_vif_from_mac80211(vif);
> +#ifdef CONFIG_IWLWIFI_DEBUGFS
> struct iwl_mvm *mvm = mvmvif->mvm;
> struct iwl_fw_dbg_trigger_missed_bcon *bcon_trig;
> struct iwl_fw_dbg_trigger_tlv *trigger;
> u32 stop_trig_missed_bcon, stop_trig_missed_bcon_since_rx;
> +#endif
> u32 rx_missed_bcon, rx_missed_bcon_since_rx;
>
> if (mvmvif->id != (u16)le32_to_cpu(missed_beacons->mac_id))
> @@ -1395,6 +1397,7 @@ static void iwl_mvm_beacon_loss_iterator(void *_data, u8 *mac,
> IWL_MVM_MISSED_BEACONS_THRESHOLD)
> ieee80211_beacon_loss(vif);
>
> +#ifdef CONFIG_IWLWIFI_DEBUGFS
> if (!iwl_fw_dbg_trigger_enabled(mvm->fw,
> FW_DBG_TRIGGER_MISSED_BEACONS))
> return;
> @@ -1414,6 +1417,7 @@ static void iwl_mvm_beacon_loss_iterator(void *_data, u8 *mac,
> if (rx_missed_bcon_since_rx >= stop_trig_missed_bcon_since_rx ||
> rx_missed_bcon >= stop_trig_missed_bcon)
> iwl_mvm_fw_dbg_collect_trig(mvm, trigger, NULL, 0);
> +#endif
> }
>
> int iwl_mvm_rx_missed_beacons_notif(struct iwl_mvm *mvm,
> diff --git a/drivers/net/wireless/iwlwifi/mvm/phy-ctxt.c b/drivers/net/wireless/iwlwifi/mvm/phy-ctxt.c
> index 1bd10ed..850c72c 100644
> --- a/drivers/net/wireless/iwlwifi/mvm/phy-ctxt.c
> +++ b/drivers/net/wireless/iwlwifi/mvm/phy-ctxt.c
> @@ -175,8 +175,11 @@ static void iwl_mvm_phy_ctxt_cmd_data(struct iwl_mvm *mvm,
> cmd->rxchain_info |= cpu_to_le32(idle_cnt << PHY_RX_CHAIN_CNT_POS);
> cmd->rxchain_info |= cpu_to_le32(active_cnt <<
> PHY_RX_CHAIN_MIMO_CNT_POS);
> +
> +#ifdef CONFIG_IWLWIFI_DEBUGFS
> if (unlikely(mvm->dbgfs_rx_phyinfo))
> cmd->rxchain_info = cpu_to_le32(mvm->dbgfs_rx_phyinfo);
> +#endif
>
> cmd->txchain_info = cpu_to_le32(iwl_mvm_get_valid_tx_ant(mvm));
> }
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2015-03-04 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 17:59 Alban Gruin
2015-03-04 18:25 ` Grumbach, Emmanuel [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=1425493551.2820.5.camel@egrumbacBox \
--to=emmanuel.grumbach@intel.com \
--cc=alban.gruin@gmail.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®