linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: iwlwifi-next 2013-06-14
Date: Fri, 14 Jun 2013 12:48:50 +0200	[thread overview]
Message-ID: <1371206930.8278.8.camel@jlt4.sipsolutions.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]

John,

Here are some more things for -next. I will have another pull request
some time next week because we're preparing to release the firmware for
the 7000 series devices, and unfortunately that will require an API
bump.

This time I have a number of cleanups, a small fix from Emmanuel and two
performance improvements that combined reduce our driver's CPU
utilisation as much as 75% in high TX-throughput scenarios.

johannes


The following changes since commit 8eb3871076875f247483f4a1fe6713e6d440c53e:

  iwlwifi: mvm: Update the supported interface combinations (2013-06-11 20:17:06 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git for-john

for you to fetch changes up to adaf69186c24100d34c2fb107dacd33546cad3c5:

  iwlwifi: mvm: remove obsolete comment (2013-06-13 16:43:16 +0200)

----------------------------------------------------------------
David Spinadel (1):
      iwlwifi: remove calib channel section from PHY DB

Emmanuel Grumbach (2):
      iwlwifi: mvm: take the seqno from packet if transmit failed
      iwlwifi: mvm: remove obsolete comment

Johannes Berg (5):
      iwlwifi: make TX seqno validation more efficient
      iwlwifi: pcie: don't read INTA register in ICT IRQ handler
      iwlwifi: reduce debug ifdefs using the optimiser
      iwlwifi: mvm: mark scratch area in TX command
      iwlwifi: create opmode/device dependencies

Oren Givon (1):
      iwlwifi: mvm: removed an unused parameter from a function

 drivers/net/wireless/iwlwifi/Makefile        |  6 ++--
 drivers/net/wireless/iwlwifi/dvm/main.c      |  7 -----
 drivers/net/wireless/iwlwifi/iwl-config.h    |  4 +++
 drivers/net/wireless/iwlwifi/iwl-debug.h     |  4 +++
 drivers/net/wireless/iwlwifi/iwl-modparams.h |  2 ++
 drivers/net/wireless/iwlwifi/iwl-phy-db.c    | 36 ++---------------------
 drivers/net/wireless/iwlwifi/mvm/d3.c        | 15 +++++-----
 drivers/net/wireless/iwlwifi/mvm/fw-api-tx.h |  9 +++---
 drivers/net/wireless/iwlwifi/mvm/tx.c        |  5 ++--
 drivers/net/wireless/iwlwifi/pcie/drv.c      |  4 +++
 drivers/net/wireless/iwlwifi/pcie/internal.h |  2 ++
 drivers/net/wireless/iwlwifi/pcie/rx.c       | 44 ++++++++++------------------
 drivers/net/wireless/iwlwifi/pcie/tx.c       | 10 +++----
 13 files changed, 58 insertions(+), 90 deletions(-)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2013-06-14 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 10:48 Johannes Berg [this message]
2013-06-14 17:32 ` pull-request: iwlwifi-next 2013-06-14 John W. Linville

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=1371206930.8278.8.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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;
as well as URLs for NNTP newsgroup(s).