From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Aloka Dixit <quic_alokad@quicinc.com>,
<johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v8 0/5] Additional processing in beacon updates (v8)
Date: Wed, 16 Aug 2023 11:38:28 -0700 [thread overview]
Message-ID: <46340c48-285e-4e2a-b6e9-802f922f0c2c@quicinc.com> (raw)
In-Reply-To: <20230727174100.11721-1-quic_alokad@quicinc.com>
On 7/27/2023 10:40 AM, Aloka Dixit wrote:
> v8: Patches #1, #2 are new in this version which allow resetting
> the interval to 0 once set to non-zero which was not possible earlier.
> No functional changes to the remaining three patches from v7 here:
> https://patchwork.kernel.org/project/linux-wireless/list/?series=693804&state=%2A&archive=both
>
> v7: Resolved conflicts with MLO code changes.
>
> FILS discovery and unsolicited broadcast probe response transmissions
> are configured as part of NL80211_CMD_START_AP. The configurations
> may get changed whenever there is a change in beacon, e. g. when
> a channel switch operation completes the new templates will be sent
> by the userspace which reflects the new channel bandwidth. Process the
> attributes for these features in NL80211_CMD_SET_BEACON as well.
>
> - Replace the check for interval (for both features) with a new flag
> 'update' which is set only when the userspace requests an update to
> the configuration. This allows the interval to be set to 0 and
> templates deleted which wasn't allowed earlier as the attributes got
> processed only if the interval was non-zero.
> - Modify the local variable in nl80211_set_beacon() and input parameter
> to rdev_change_beacon() from type struct cfg80211_beacon_data to
> type struct cfg80211_ap_settings to support the new processing.
> - Modify ieee80211_change_beacon() to reflect the new input parameter type.
> - Modify driver specific functions pointed by change_beacon to reflect
> the new input parameter type.
> - Add the missing implementation in nl80211 and mac80211 to process
> FILS discovery and unsolicited broadcast probe response configurations.
>
>
> Aloka Dixit (5):
> wifi: nl80211: fixes to FILS discovery updates
> wifi: mac80211: fixes in FILS discovery updates
> wifi: cfg80211: modify prototype for change_beacon
> wifi: nl80211: additions to NL80211_CMD_SET_BEACON
> wifi: mac80211: additions to change_beacon()
>
> drivers/net/wireless/ath/ath6kl/cfg80211.c | 4 +-
> drivers/net/wireless/ath/wil6210/cfg80211.c | 3 +-
> .../broadcom/brcm80211/brcmfmac/cfg80211.c | 4 +-
> .../net/wireless/marvell/mwifiex/cfg80211.c | 3 +-
> .../wireless/microchip/wilc1000/cfg80211.c | 4 +-
> .../net/wireless/quantenna/qtnfmac/cfg80211.c | 4 +-
> .../staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 6 +-
> include/net/cfg80211.h | 6 +-
> include/uapi/linux/nl80211.h | 11 +-
> net/mac80211/cfg.c | 102 ++++++++++--------
> net/wireless/nl80211.c | 47 ++++++--
> net/wireless/rdev-ops.h | 2 +-
> net/wireless/trace.h | 54 +++++-----
> 13 files changed, 159 insertions(+), 91 deletions(-)
>
>
> base-commit: b2090d93d4b6f1c72a9793d5a171806b8468b7cb
for the series:
Reviewed-by: Jeff Johnson <quic_jjohnson@quicinc.com>
next prev parent reply other threads:[~2023-08-16 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 17:40 [PATCH v8 0/5] Additional processing in beacon updates (v8) Aloka Dixit
2023-07-27 17:40 ` [PATCH v8 1/5] wifi: nl80211: fixes to FILS discovery updates Aloka Dixit
2023-07-27 17:40 ` [PATCH v8 2/5] wifi: mac80211: fixes in " Aloka Dixit
2023-07-27 17:40 ` [PATCH v8 3/5] wifi: cfg80211: modify prototype for change_beacon Aloka Dixit
2023-07-27 17:40 ` [PATCH v8 4/5] wifi: nl80211: additions to NL80211_CMD_SET_BEACON Aloka Dixit
2023-07-27 17:41 ` [PATCH v8 5/5] wifi: mac80211: additions to change_beacon() Aloka Dixit
2023-08-16 18:38 ` Jeff Johnson [this message]
2023-08-17 18:04 ` [PATCH v8 0/5] Additional processing in beacon updates (v8) Aloka Dixit
2023-09-06 17:52 ` Aloka Dixit
2023-09-13 10:26 ` Johannes Berg
2023-09-18 22:29 ` Aloka Dixit
2023-09-25 7:17 ` 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=46340c48-285e-4e2a-b6e9-802f922f0c2c@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.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;
as well as URLs for NNTP newsgroup(s).