From: Kalle Valo <kvalo@kernel.org>
To: Aloka Dixit <quic_alokad@quicinc.com>
Cc: <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v5 1/3] cfg80211: additional processing in NL80211_CMD_SET_BEACON
Date: Tue, 17 May 2022 07:45:15 +0300 [thread overview]
Message-ID: <87v8u4wyw4.fsf@kernel.org> (raw)
In-Reply-To: <20220516202454.4925-2-quic_alokad@quicinc.com> (Aloka Dixit's message of "Mon, 16 May 2022 13:24:52 -0700")
Aloka Dixit <quic_alokad@quicinc.com> writes:
> FILS discovery and unsolicited broadcast probe response transmissions
> are configured as part of NL80211_CMD_START_AP, however both stop
> after userspace uses the NL80211_CMD_SET_BEACON command as these
> attributes are not processed in that command.
>
> - Add the missing implementation.
> - 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.
>
> Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
> ---
> include/net/cfg80211.h | 2 +-
> net/wireless/nl80211.c | 28 ++++++++++++++++++----
> net/wireless/rdev-ops.h | 2 +-
> net/wireless/trace.h | 52 +++++++++++++++++++++++------------------
> 4 files changed, 55 insertions(+), 29 deletions(-)
>
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index 97a5804ccdcf..880ade4a0430 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -4200,7 +4200,7 @@ struct cfg80211_ops {
> int (*start_ap)(struct wiphy *wiphy, struct net_device *dev,
> struct cfg80211_ap_settings *settings);
> int (*change_beacon)(struct wiphy *wiphy, struct net_device *dev,
> - struct cfg80211_beacon_data *info);
> + struct cfg80211_ap_settings *info);
Shouldn't patch 3 folded into patch 1? I don't see how patch 1 as is
would compile without warnings.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-05-17 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 20:24 [PATCH v5 0/3] additional processing in NL80211_CMD_SET_BEACON Aloka Dixit
2022-05-16 20:24 ` [PATCH v5 1/3] cfg80211: " Aloka Dixit
2022-05-17 4:45 ` Kalle Valo [this message]
2022-05-17 10:50 ` Johannes Berg
2022-05-17 18:53 ` Aloka Dixit
2022-05-16 20:24 ` [PATCH v5 2/3] mac80211: process additional data during beacon change Aloka Dixit
2022-05-16 20:24 ` [PATCH v5 3/3] drivers: modify prototype for beacon change functions 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=87v8u4wyw4.fsf@kernel.org \
--to=kvalo@kernel.org \
--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 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.