linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-2023-03-23
Date: Thu, 23 Mar 2023 11:03:32 +0000 (UTC)	[thread overview]
Message-ID: <20230323110332.C4FE4C433D2@smtp.kernel.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 96c069508377547f913e7265a80fffe9355de592:

  wifi: cfg80211: fix MLO connection ownership (2023-03-10 11:47:25 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git tags/wireless-2023-03-23

for you to fetch changes up to f355f70145744518ca1d9799b42f4a8da9aa0d36:

  wifi: mac80211: fix mesh path discovery based on unicast packets (2023-03-22 13:46:46 +0100)

----------------------------------------------------------------
wireless fixes for v6.3

Third set of fixes for v6.3. mt76 has two kernel crash fixes and
adding back 160 MHz channel support for mt7915. mac80211 has fixes for
a race in transmit path and two mesh related fixes. iwlwifi also has
fixes for races.

----------------------------------------------------------------
Alexander Wetzel (1):
      wifi: mac80211: Serialize ieee80211_handle_wake_tx_queue()

Felix Fietkau (3):
      wifi: mt76: mt7915: add back 160MHz channel width support for MT7915
      wifi: mac80211: fix qos on mesh interfaces
      wifi: mac80211: fix mesh path discovery based on unicast packets

Johannes Berg (2):
      wifi: iwlwifi: mvm: fix mvmtxq->stopped handling
      wifi: iwlwifi: mvm: protect TXQ list manipulation

Krzysztof Kozlowski (1):
      wifi: mwifiex: mark OF related data as maybe unused

Lorenzo Bianconi (2):
      wifi: mt76: do not run mt76_unregister_device() on unregistered hw
      wifi: mt76: connac: do not check WED status for non-mmio devices

 drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c  | 50 ++++++++--------------
 drivers/net/wireless/intel/iwlwifi/mvm/mvm.h       |  6 ++-
 drivers/net/wireless/intel/iwlwifi/mvm/ops.c       |  6 ++-
 drivers/net/wireless/intel/iwlwifi/mvm/sta.c       | 29 ++++++++++---
 drivers/net/wireless/marvell/mwifiex/pcie.c        |  2 +-
 drivers/net/wireless/marvell/mwifiex/sdio.c        |  2 +-
 drivers/net/wireless/mediatek/mt76/mac80211.c      |  8 ++++
 drivers/net/wireless/mediatek/mt76/mt76.h          |  1 +
 .../net/wireless/mediatek/mt76/mt76_connac_mcu.c   |  3 ++
 drivers/net/wireless/mediatek/mt76/mt7915/init.c   | 40 ++++++++++++-----
 net/mac80211/ieee80211_i.h                         |  3 ++
 net/mac80211/main.c                                |  2 +
 net/mac80211/rx.c                                  | 22 +++++-----
 net/mac80211/util.c                                |  3 ++
 net/mac80211/wme.c                                 |  6 ++-
 15 files changed, 119 insertions(+), 64 deletions(-)

             reply	other threads:[~2023-03-23 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 11:03 Kalle Valo [this message]
2023-03-23 23:00 ` pull-request: wireless-2023-03-23 patchwork-bot+netdevbpf

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=20230323110332.C4FE4C433D2@smtp.kernel.org \
    --to=kvalo@kernel.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).