From: Aloka Dixit <quic_alokad@quicinc.com>
To: <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>
Cc: Aloka Dixit <quic_alokad@quicinc.com>
Subject: [PATCH v4 0/4] v4: Puncturing support in AP mode
Date: Mon, 30 Jan 2023 16:12:23 -0800 [thread overview]
Message-ID: <20230131001227.25014-1-quic_alokad@quicinc.com> (raw)
- Moved bitmap validation from MAC80211 to CFG80211.
- Combined start_ap() and switch_channel() patches for a given module.
- Changed the order of patches.
Aloka Dixit (4):
cfg80211: move puncturing bitmap validation from mac80211
wifi: nl80211: validate and configure puncturing bitmap
wifi: cfg80211: include puncturing bitmap in channel switch events
wifi: mac80211: configure puncturing bitmap
drivers/net/wireless/ath/ath6kl/cfg80211.c | 2 +-
drivers/net/wireless/marvell/mwifiex/11h.c | 2 +-
include/net/cfg80211.h | 26 +++++++-
include/net/mac80211.h | 3 +
include/uapi/linux/nl80211.h | 12 ++++
net/mac80211/cfg.c | 23 ++++++-
net/mac80211/mlme.c | 77 +++-------------------
net/wireless/chan.c | 69 +++++++++++++++++++
net/wireless/nl80211.c | 58 ++++++++++++++--
net/wireless/trace.h | 24 ++++---
10 files changed, 205 insertions(+), 91 deletions(-)
base-commit: 4ca69027691a0039279b64cfa0aa511d9c9fde59
prerequisite-patch-id: f3e39c8c03c23c977baa8946066285e597b93c7e
--
2.39.0
next reply other threads:[~2023-01-31 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 0:12 Aloka Dixit [this message]
2023-01-31 0:12 ` [PATCH v4 1/4] cfg80211: move puncturing bitmap validation from mac80211 Aloka Dixit
2023-01-31 0:12 ` [PATCH v4 2/4] wifi: nl80211: validate and configure puncturing bitmap Aloka Dixit
2023-01-31 0:12 ` [PATCH v4 3/4] wifi: cfg80211: include puncturing bitmap in channel switch events Aloka Dixit
2023-01-31 0:12 ` [PATCH v4 4/4] wifi: mac80211: configure puncturing bitmap Aloka Dixit
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=20230131001227.25014-1-quic_alokad@quicinc.com \
--to=quic_alokad@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).