All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-2023-10-24
Date: Tue, 24 Oct 2023 12:35:41 +0200	[thread overview]
Message-ID: <20231024103540.19198-2-johannes@sipsolutions.net> (raw)

Hi,

We have a couple of last-minute fixes for some issues.

Note that this introduces a merge conflict with -next,
which Stephen reported and (correctly) resolved here:
https://lore.kernel.org/linux-wireless/20231024112424.7de86457@canb.auug.org.au/
Basically just context - use the ieee80211_is_protected_dual_of_public_action()
check from this pull request, and the return code
RX_DROP_U_UNPROT_UNICAST_PUB_ACTION from -next.

Please pull and let us know if there's any problem.

Thanks,
johannes



The following changes since commit f2ac54ebf85615a6d78f5eb213a8bbeeb17ebe5d:

  net: rfkill: reduce data->mtx scope in rfkill_fop_open (2023-10-11 16:55:10 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git tags/wireless-2023-10-24

for you to fetch changes up to 91535613b6090fc968c601d11d4e2f16b333713c:

  wifi: mac80211: don't drop all unprotected public action frames (2023-10-23 13:25:30 +0200)

----------------------------------------------------------------
Three more fixes:
 - don't drop all unprotected public action frames since
   some don't have a protected dual
 - fix pointer confusion in scanning code
 - fix warning in some connections with multiple links

----------------------------------------------------------------
Avraham Stern (1):
      wifi: mac80211: don't drop all unprotected public action frames

Ben Greear (1):
      wifi: cfg80211: pass correct pointer to rdev_inform_bss()

Johannes Berg (1):
      wifi: cfg80211: fix assoc response warning on failed links

 include/linux/ieee80211.h | 29 +++++++++++++++++++++++++++++
 net/mac80211/rx.c         |  3 +--
 net/wireless/mlme.c       |  3 ++-
 net/wireless/scan.c       |  2 +-
 4 files changed, 33 insertions(+), 4 deletions(-)


             reply	other threads:[~2023-10-24 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 10:35 Johannes Berg [this message]
2023-10-24 20:20 ` pull-request: wireless-2023-10-24 patchwork-bot+netdevbpf
2023-10-24 20:25   ` Johannes Berg
2023-10-24 20:52     ` Jakub Kicinski
2023-10-24 20:54       ` Johannes Berg
2023-10-24 21:01         ` Jakub Kicinski
2023-10-24 21:03           ` Johannes Berg

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=20231024103540.19198-2-johannes@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.