Linux wireless drivers development
 help / color / mirror / Atom feed
From: Benjamin Berg <benjamin@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
	Brian Norris <briannorris@chromium.org>,
	Francesco Dolcini <francesco@dolcini.it>,
	Ajay Singh <ajay.kathat@microchip.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Jeff Chen <jeff.chen_1@nxp.com>,
	Igor Mitsyanko <imitsyanko@quantenna.com>,
	Sergey Matyukevich <geomatsi@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	brcm80211@lists.linux.dev, libertas-dev@lists.infradead.org,
	Miri Korenblit <miriam.rachel.korenblit@intel.com>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Benjamin Berg <benjamin.berg@intel.com>
Subject: [PATCH wireless-next v3 0/7] Add support for Control Integrity Protocol (CIP)
Date: Mon, 21 Sep 2026 14:40:49 +0200	[thread overview]
Message-ID: <20260921124048.4146576-9-benjamin@sipsolutions.net> (raw)

From: Benjamin Berg <benjamin.berg@intel.com>

This adds the mac80211 support for the new key type and using the
pairwise key for control frame protection (CFP).

v3:
- Add debugfs patches for hwsim testing
- Update for REVmf D3.0
- Configure CIP in hwsim for further interface types

v2:
- adjust rtl8723bs stating driver
- fix nl80211 attribute insertion

Benjamin Berg (6):
  wifi: mac80211: add key link_id to debugfs
  wifi: cfg80211: add Control Integrity Protocol (CIP) APIs
  wifi: mac80211: add cigtk parameter to ieee80211_gtk_rekey_add
  wifi: mac80211: add helpers to parse/generate CIP Capabilities
  wifi: mac80211: add Control Integrity Protocol handling
  wifi: mac80211_hwsim: claim support for Control Integrity Protocol

Johannes Berg (1):
  wifi: mac80211: add key flags to debugfs

 drivers/net/wireless/ath/ath6kl/cfg80211.c    |  10 +-
 drivers/net/wireless/ath/wil6210/cfg80211.c   |  13 +-
 .../broadcom/brcm80211/brcmfmac/cfg80211.c    |  11 +-
 drivers/net/wireless/intel/iwlwifi/mld/d3.c   |   6 +-
 drivers/net/wireless/intel/iwlwifi/mvm/d3.c   |   6 +-
 drivers/net/wireless/marvell/libertas/cfg.c   |   6 +-
 .../net/wireless/marvell/mwifiex/cfg80211.c   |  12 +-
 .../wireless/microchip/wilc1000/cfg80211.c    |  13 +-
 drivers/net/wireless/nxp/nxpwifi/cfg80211.c   |  11 +-
 .../net/wireless/quantenna/qtnfmac/cfg80211.c |   8 +-
 drivers/net/wireless/realtek/rtw89/wow.c      |   6 +-
 .../wireless/virtual/mac80211_hwsim_main.c    |  35 +++++
 .../staging/rtl8723bs/os_dep/ioctl_cfg80211.c |   9 +-
 include/linux/ieee80211.h                     |  22 ++++
 include/net/cfg80211.h                        |  19 ++-
 include/net/mac80211.h                        |  11 +-
 include/uapi/linux/nl80211.h                  |  14 ++
 net/mac80211/cfg.c                            |  41 ++++--
 net/mac80211/debugfs_key.c                    |  18 ++-
 net/mac80211/ieee80211_i.h                    |   5 +
 net/mac80211/key.c                            |  96 ++++++++++----
 net/mac80211/key.h                            |   3 +-
 net/mac80211/mlme.c                           |  20 ++-
 net/mac80211/parse.c                          |   4 +
 net/mac80211/sta_info.h                       |   2 +
 net/mac80211/util.c                           |  19 +++
 net/wireless/core.h                           |   7 +-
 net/wireless/ibss.c                           |   3 +-
 net/wireless/nl80211.c                        | 124 ++++++++++++++----
 net/wireless/rdev-ops.h                       |  23 ++--
 net/wireless/sme.c                            |  10 +-
 net/wireless/trace.h                          |  37 +++---
 net/wireless/util.c                           |  40 +++++-
 net/wireless/wext-compat.c                    |   8 +-
 34 files changed, 532 insertions(+), 140 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-09-21 12:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 12:40 Benjamin Berg [this message]
2026-09-21 12:40 ` [PATCH wireless-next v3 1/7] wifi: mac80211: add key flags to debugfs Benjamin Berg
2026-09-21 12:40 ` [PATCH wireless-next v3 2/7] wifi: mac80211: add key link_id " Benjamin Berg
2026-09-21 12:40 ` [PATCH wireless-next v3 3/7] wifi: cfg80211: add Control Integrity Protocol (CIP) APIs Benjamin Berg
2026-09-21 12:40 ` [PATCH wireless-next v3 4/7] wifi: mac80211: add cigtk parameter to ieee80211_gtk_rekey_add Benjamin Berg
2026-09-21 12:40 ` [PATCH wireless-next v3 5/7] wifi: mac80211: add helpers to parse/generate CIP Capabilities Benjamin Berg
2026-09-21 12:40 ` [PATCH wireless-next v3 6/7] wifi: mac80211: add Control Integrity Protocol handling Benjamin Berg
2026-09-21 12:40 ` [PATCH wireless-next v3 7/7] wifi: mac80211_hwsim: claim support for Control Integrity Protocol Benjamin 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=20260921124048.4146576-9-benjamin@sipsolutions.net \
    --to=benjamin@sipsolutions.net \
    --cc=ajay.kathat@microchip.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=benjamin.berg@intel.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=briannorris@chromium.org \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=francesco@dolcini.it \
    --cc=geomatsi@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imitsyanko@quantenna.com \
    --cc=jeff.chen_1@nxp.com \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    --cc=pkshih@realtek.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