From: Johannes Berg <johannes@sipsolutions.net>
To: Kieran Frewen <kieran.frewen@morsemicro.com>
Cc: linux-wireless@vger.kernel.org, quic_jjohnson@quicinc.com
Subject: Re: [PATCH v3 03/12] mac80211: S1G beacon/short beacon support
Date: Tue, 06 Sep 2022 11:43:31 +0200 [thread overview]
Message-ID: <d58015ea844a0b56ea39de5f63b7f6889afcd918.camel@sipsolutions.net> (raw)
In-Reply-To: <20220906044812.7609-4-kieran.frewen@morsemicro.com>
On Tue, 2022-09-06 at 16:48 +1200, Kieran Frewen wrote:
> If configured, use the S1G short beacon format. The S1G short beacon
> format includes a limited set of information elements.
>
> Signed-off-by: Kieran Frewen <kieran.frewen@morsemicro.com>
> ---
> include/net/cfg80211.h | 2 +-
> include/net/mac80211.h | 1 +
> net/mac80211/cfg.c | 1 +
> net/mac80211/ieee80211_i.h | 1 +
> net/mac80211/tx.c | 14 +++++++++++++-
> 5 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index 945e7700de66..b750b2ad246b 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -1328,7 +1328,7 @@ struct cfg80211_ap_settings {
>
> struct cfg80211_beacon_data beacon;
>
> - int beacon_interval, dtim_period;
> + int beacon_interval, dtim_period, short_beacon_period;
>
One way or the other, this doesn't belong into this patch - you should
reorder so cfg80211 comes first and then mac80211 can use it, and then
this change goes into the cfg80211 patch.
johannes
next prev parent reply other threads:[~2022-09-06 9:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 4:48 [PATCH v3 00/12] Additional Support for 802.11ah (S1G) Kieran Frewen
2022-09-06 4:48 ` [PATCH v3 01/12] cfg80211: regulatory: extend regulatory support for S1G Kieran Frewen
2022-09-06 9:36 ` Johannes Berg
2022-09-21 22:10 ` Kieran Frewen
2022-09-06 4:48 ` [PATCH v3 02/12] mac80211: update TIM for S1G specification changes Kieran Frewen
2022-09-06 9:38 ` Johannes Berg
2022-09-06 4:48 ` [PATCH v3 03/12] mac80211: S1G beacon/short beacon support Kieran Frewen
2022-09-06 9:40 ` Johannes Berg
2022-09-06 9:43 ` Johannes Berg [this message]
2022-09-06 4:48 ` [PATCH v3 04/12] nl80211: support setting S1G short beacon period Kieran Frewen
2022-09-06 9:42 ` Johannes Berg
2022-09-06 4:48 ` [PATCH v3 05/12] nl80211: support advertising S1G capabilities Kieran Frewen
2022-09-06 4:48 ` [PATCH v3 06/12] mac80211: support ieee80211_ext format Kieran Frewen
2022-09-06 9:45 ` Johannes Berg
2022-09-06 4:48 ` [PATCH v3 07/12] mac80211: S1G capabilities information element in probe request Kieran Frewen
2022-09-06 9:47 ` Johannes Berg
2022-09-06 4:48 ` [PATCH v3 08/12] cfg80211: S1G rate flags Kieran Frewen
2022-09-06 4:48 ` [PATCH v3 09/12] nl80211: support advertising S1G rate information Kieran Frewen
2022-09-06 4:48 ` [PATCH v3 10/12] mac80211: support S1G rate encoding Kieran Frewen
2022-09-06 4:48 ` [PATCH v3 11/12] cfg80211: support for calculating S1G bitrates Kieran Frewen
2022-09-06 9:51 ` Johannes Berg
2022-09-06 4:48 ` [PATCH v3 12/12] mac80211_hwsim: support for S1G rate information Kieran Frewen
2022-11-07 20:09 ` [PATCH v3 00/12] Additional Support for 802.11ah (S1G) Kieran Frewen
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=d58015ea844a0b56ea39de5f63b7f6889afcd918.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kieran.frewen@morsemicro.com \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@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).