From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Abhijeet Kolekar <abhijeet.kolekar@intel.com>
Cc: linux-wireless@vger.kernel.org,
Intel Linux Wireless <ilw@linux.intel.com>
Subject: [RFC] iwl3945: remove check_plcp_health
Date: Tue, 25 Jan 2011 10:35:28 +0100 [thread overview]
Message-ID: <20110125093507.GA6429@redhat.com> (raw)
This patch helps some users currently complaining about iwl3945
performance.
https://bugzilla.redhat.com/show_bug.cgi?id=654599
https://bugs.launchpad.net/ubuntu/maverick/+source/linux/+bug/621265/+index?comments=all
Patch does not helps all users, but they seems to be affected
by different bug or bugs.
Patch effectively reverts commit a29576a7844326c5223f4d4adbfd3f4d64173d4c
"iwl3945: add plcp error checking". It is minimal fix intended to
-stable posting. I will post cleaning up patch, if fix will be accepted.
---
drivers/net/wireless/iwlwifi/iwl-3945.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-3945.c b/drivers/net/wireless/iwlwifi/iwl-3945.c
index 8cacb4e..eb916d7 100644
--- a/drivers/net/wireless/iwlwifi/iwl-3945.c
+++ b/drivers/net/wireless/iwlwifi/iwl-3945.c
@@ -2832,7 +2832,6 @@ static struct iwl_lib_ops iwl3945_lib = {
.config_ap = iwl3945_config_ap,
.manage_ibss_station = iwl3945_manage_ibss_station,
.recover_from_tx_stall = iwl_bg_monitor_recover,
- .check_plcp_health = iwl3945_good_plcp_health,
.debugfs_ops = {
.rx_stats_read = iwl3945_ucode_rx_stats_read,
--
1.7.1
next reply other threads:[~2011-01-25 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 9:35 Stanislaw Gruszka [this message]
2011-01-25 14:56 ` [RFC] iwl3945: remove check_plcp_health wwguy
2011-01-25 15:14 ` John W. Linville
2011-01-26 7:15 ` Stanislaw Gruszka
2011-02-08 7:35 ` Stanislaw Gruszka
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=20110125093507.GA6429@redhat.com \
--to=sgruszka@redhat.com \
--cc=abhijeet.kolekar@intel.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--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).