linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-drivers-2020-03-05
Date: Thu,  5 Mar 2020 13:46:03 +0000 (UTC)	[thread overview]
Message-ID: <20200305134603.734F2C433A2@smtp.codeaurora.org> (raw)

Hi,

here's a pull request to net tree, more info below. Please let me know if there
are any problems.

Kalle

The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:

  Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git tags/wireless-drivers-2020-03-05

for you to fetch changes up to b102f0c522cf668c8382c56a4f771b37d011cda2:

  mt76: fix array overflow on receiving too many fragments for a packet (2020-03-03 17:30:25 +0200)

----------------------------------------------------------------
wireless-drivers fixes for v5.6

Second set of fixes for v5.6. Only two small fixes this time.

iwlwifi

* fix another initialisation regression with 3168 devices

mt76

* fix memory corruption with too many rx fragments

----------------------------------------------------------------
Dan Moulding (1):
      iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices

Felix Fietkau (1):
      mt76: fix array overflow on receiving too many fragments for a packet

 drivers/net/wireless/intel/iwlwifi/mvm/nvm.c | 3 ++-
 drivers/net/wireless/mediatek/mt76/dma.c     | 9 ++++++---
 2 files changed, 8 insertions(+), 4 deletions(-)

             reply	other threads:[~2020-03-05 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 13:46 Kalle Valo [this message]
2020-03-05 23:05 ` pull-request: wireless-drivers-2020-03-05 David Miller

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=20200305134603.734F2C433A2@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).