All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Aloka Dixit <alokad@codeaurora.org>, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH v2 1/2] nl80211: FILS discovery/bcast probe resp support
Date: Tue, 26 May 2020 10:18:34 +0200	[thread overview]
Message-ID: <0c89ad68-67bf-7ade-7702-1695bb7274cb@broadcom.com> (raw)
In-Reply-To: <20200526000913.30434-2-alokad@codeaurora.org>

On 5/26/2020 2:09 AM, Aloka Dixit wrote:
> This patch adds new attribute, NL80211_ATTR_FD_BCASTPRESP_CFG
> to configure FILS discovery and broadcast probe response in 6GHz
> for in-band discovery.
> 
> Only one of the two is active at a time to reduce broadcast
> packets over the air.
> 
> Maximum packet interval can be 20 TUs.
> Packet interval set to 0 disables FILS discovery and broadcast
> probe response transmission.
> 
> Signed-off-by: Aloka Dixit <alokad@codeaurora.org>
> Reported-by: kbuild test robot <lkp@intel.com>

huh? what is reported. Oh, guess it is the reason for having v2. Don't 
think this tag is useful for that. Only useful if v1 would have been 
applied and this patch would fix that.

> ---
> v2: Fixed warning.
> 
>   include/net/cfg80211.h       | 26 ++++++++++++++++
>   include/uapi/linux/nl80211.h | 27 +++++++++++++++++
>   net/wireless/nl80211.c       | 58 ++++++++++++++++++++++++++++++++++++
>   3 files changed, 111 insertions(+)
> 
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index a82fc59a1d82..e4bc03947005 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -957,6 +957,8 @@ struct cfg80211_crypto_settings {
>    * @assocresp_ies_len: length of assocresp_ies in octets
>    * @probe_resp_len: length of probe response template (@probe_resp)
>    * @probe_resp: probe response template (AP mode only)
> + * @bcast_presp: Broadcast probe response template (AP mode only)
> + * @fils_disc: FILS discovery template (AP mode only)
>    * @ftm_responder: enable FTM responder functionality; -1 for no change
>    *	(which also implies no change in LCI/civic location data)
>    * @lci: Measurement Report element content, starting with Measurement Token
> @@ -965,6 +967,8 @@ struct cfg80211_crypto_settings {
>    *	Token (measurement type 11)
>    * @lci_len: LCI data length
>    * @civicloc_len: Civic location data length
> + * @bcast_presp_len: Broadcast probe response template length
> + * @fils_disc_len: FILS discovery template length
>    */
>   struct cfg80211_beacon_data {
>   	const u8 *head, *tail;
> @@ -974,6 +978,8 @@ struct cfg80211_beacon_data {
>   	const u8 *probe_resp;
>   	const u8 *lci;
>   	const u8 *civicloc;
> +	const u8 *bcast_presp;
> +	const u8 *fils_disc;

This is not really beacon data, now is it?

Regards,
Arend

  reply	other threads:[~2020-05-26  8:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  0:09 [PATCH v2 0/2] FILS discovery and bcast probe resp support Aloka Dixit
2020-05-26  0:09 ` [PATCH v2 1/2] nl80211: FILS discovery/bcast " Aloka Dixit
2020-05-26  8:18   ` Arend Van Spriel [this message]
2020-05-27  8:26     ` Johannes Berg
2020-05-26  0:09 ` [PATCH v2 2/2] mac80211: FILS disc/bcast probe resp config 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=0c89ad68-67bf-7ade-7702-1695bb7274cb@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=alokad@codeaurora.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.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.