Linux wireless drivers development
 help / color / mirror / Atom feed
From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, Wey-Yi Guy <wey-yi.w.guy@intel.com>
Subject: [PATCH 00/12] update for 3.2
Date: Thu, 22 Sep 2011 15:14:48 -0700	[thread overview]
Message-ID: <1316729700-1770-1-git-send-email-wey-yi.w.guy@intel.com> (raw)

We fix some performance issue cause by rate scale and sequence control in
transport layer.
We fix number of scan related issue mainly for P2P
Plus number of small cleanup changes 

Emmanuel Grumbach (3):
  iwlagn: set the sequence control from the transport layer
  iwlagn: update rate scaling with BA notifications
  iwlagn: use kcalloc when possible for array allocation

Johannes Berg (7):
  iwlagn: fix dangling scan request
  iwlagn: fix slot programming
  iwlagn: remove Kelvin support
  iwlagn: make iwl_scan_cancel_timeout void
  iwlagn: refactor scan complete
  iwlagn: move iwl_process_scan_complete up
  iwlagn: fix scan complete processing

Wey-Yi Guy (2):
  MAINTAINERS: update iwlwifi
  iwlagn: add debugging to show probe related info in scan notification

these patches are also available from wireless-next-2.6 branch on
 git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi.git

Because the file system problem, all the patches are not push into 
git.kernel.org yet. I will push as soon as the file system issue addressed

 MAINTAINERS                                   |    2 +-
 drivers/net/wireless/iwlwifi/iwl-agn-rxon.c   |    2 +-
 drivers/net/wireless/iwlwifi/iwl-agn-tt.c     |   18 +--
 drivers/net/wireless/iwlwifi/iwl-agn-tx.c     |   16 ++-
 drivers/net/wireless/iwlwifi/iwl-core.c       |    6 +-
 drivers/net/wireless/iwlwifi/iwl-core.h       |    4 +-
 drivers/net/wireless/iwlwifi/iwl-dev.h        |    2 +-
 drivers/net/wireless/iwlwifi/iwl-eeprom.c     |    5 +-
 drivers/net/wireless/iwlwifi/iwl-scan.c       |  179 +++++++++++++++----------
 drivers/net/wireless/iwlwifi/iwl-shared.h     |    1 +
 drivers/net/wireless/iwlwifi/iwl-trans-pcie.c |   15 ++-
 11 files changed, 142 insertions(+), 108 deletions(-)


             reply	other threads:[~2011-09-22 23:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 22:14 Wey-Yi Guy [this message]
2011-09-22 22:14 ` [PATCH 01/12] MAINTAINERS: update iwlwifi Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 02/12] iwlagn: set the sequence control from the transport layer Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 03/12] iwlagn: add debugging to show probe related info in scan notification Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 04/12] iwlagn: update rate scaling with BA notifications Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 05/12] iwlagn: use kcalloc when possible for array allocation Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 06/12] iwlagn: fix dangling scan request Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 07/12] iwlagn: fix slot programming Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 08/12] iwlagn: remove Kelvin support Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 09/12] iwlagn: make iwl_scan_cancel_timeout void Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 10/12] iwlagn: refactor scan complete Wey-Yi Guy
2011-09-22 22:14 ` [PATCH 11/12] iwlagn: move iwl_process_scan_complete up Wey-Yi Guy
2011-09-22 22:15 ` [PATCH 12/12] iwlagn: fix scan complete processing Wey-Yi Guy

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=1316729700-1770-1-git-send-email-wey-yi.w.guy@intel.com \
    --to=wey-yi.w.guy@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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