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 2013-01-03
Date: Thu, 03 Jan 2013 15:42:53 +0100	[thread overview]
Message-ID: <1357224173.9741.18.camel@jlt4.sipsolutions.net> (raw)

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

John,

I have two fixes for iwlwifi: one to fix a lost return value that was
dropped in a previous patch and could cause "nobody cared" IRQ messages,
and one to work around a firmware issue.

Please pull.

Thanks,
johannes


The following changes since commit a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:

  Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)

are available in the git repository at:

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

for you to fetch changes up to f590dcec944552f9a4a61155810f3abd17d6465d:

  iwlwifi: fix the reclaimed packet tracking upon flush queue (2013-01-03 15:31:15 +0100)

----------------------------------------------------------------
Emmanuel Grumbach (1):
      iwlwifi: fix the reclaimed packet tracking upon flush queue

Johannes Berg (1):
      iwlwifi: fix PCIe interrupt handle return value

 drivers/net/wireless/iwlwifi/dvm/tx.c  | 24 +++++++++++++++++-------
 drivers/net/wireless/iwlwifi/pcie/rx.c |  1 +
 2 files changed, 18 insertions(+), 7 deletions(-)


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

             reply	other threads:[~2013-01-03 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 14:42 Johannes Berg [this message]
2013-01-03 14:43 ` [PATCH 1/2] iwlwifi: fix PCIe interrupt handle return value Johannes Berg
2013-01-03 14:43   ` [PATCH 2/2] iwlwifi: fix the reclaimed packet tracking upon flush queue Johannes Berg
2013-01-04 21:13 ` pull-request: iwlwifi 2013-01-03 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=1357224173.9741.18.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).