From: reinette chatre <reinette.chatre@intel.com>
To: Sujith <m.sujith@gmail.com>
Cc: "Halperin, Daniel C" <daniel.c.halperin@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: iwlwifi build failure
Date: Mon, 08 Dec 2008 22:36:59 -0800 [thread overview]
Message-ID: <1228804619.30670.8.camel@rc-desk> (raw)
In-Reply-To: <18749.61316.313728.426082@localhost.localdomain>
On Mon, 2008-12-08 at 20:09 -0800, Sujith wrote:
> /home/sujith/dev/wireless-testing/drivers/net/wireless/iwlwifi/iwl-rx.c: In function 'iwl_rx_reply_rx':
> /home/sujith/dev/wireless-testing/drivers/net/wireless/iwlwifi/iwl-rx.c:1074: error: 'struct iwl_priv' has no member named 'debug_level'
>
> From my .config:
>
> CONFIG_IWLWIFI=m
> CONFIG_IWLCORE=m
> CONFIG_IWLWIFI_LEDS=y
> CONFIG_IWLWIFI_RFKILL=y
> # CONFIG_IWLWIFI_DEBUG is not set
> CONFIG_IWLAGN=m
> CONFIG_IWLAGN_SPECTRUM_MEASUREMENT=y
> CONFIG_IWLAGN_LEDS=y
> CONFIG_IWL4965=y
> CONFIG_IWL5000=y
> # CONFIG_IWL3945 is not set
>
> A missing #ifdef CONFIG_IWLWIFI_DEBUG in iwl-rx.c ?
Sorry ... please use this patch below.
diff --git a/drivers/net/wireless/iwlwifi/iwl-rx.c
b/drivers/net/wireless/iwlwifi/iwl-rx.c
index 1938e6d..0a22e94 100644
--- a/drivers/net/wireless/iwlwifi/iwl-rx.c
+++ b/drivers/net/wireless/iwlwifi/iwl-rx.c
@@ -1071,8 +1071,7 @@ void iwl_rx_reply_rx(struct iwl_priv *priv,
priv->last_rx_noise = IWL_NOISE_MEAS_NOT_AVAILABLE;
/* Set "1" to report good data frames in groups of 100 */
- if (unlikely(priv->debug_level & IWL_DL_RX))
- iwl_dbg_report_frame(priv, rx_start, len, header, 1);
+ iwl_dbg_report_frame(priv, rx_start, len, header, 1);
IWL_DEBUG_STATS_LIMIT("Rssi %d, noise %d, qual %d, TSF %llu\n",
rx_status.signal, rx_status.noise, rx_status.signal,
prev parent reply other threads:[~2008-12-09 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 4:09 iwlwifi build failure Sujith
2008-12-09 6:36 ` reinette chatre [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=1228804619.30670.8.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=daniel.c.halperin@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m.sujith@gmail.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