Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Crispin <john@phrozen.org>
Cc: linux-wireless@vger.kernel.org, Aloka Dixit <alokad@codeaurora.org>
Subject: Re: [PATCH V5 3/4] mac80211: add multiple bssid/EMA support to beacon handling
Date: Fri, 06 Nov 2020 10:31:47 +0100	[thread overview]
Message-ID: <020eb33ec1ed5cd5eb076eee7cc39a09a62bfdff.camel@sipsolutions.net> (raw)
In-Reply-To: <20201103091743.1924854-4-john@phrozen.org>

On Tue, 2020-11-03 at 10:17 +0100, John Crispin wrote:

> +/**
> + * enum ieee80211_bcn_tmpl_ema - EMA beacon generation type
> + * @IEEE80211_BCN_EMA_NONE: don't generate an EMA beacon.
> + * @IEEE80211_BCN_EMA_NEXT: generate the next periodicity beacon.
> + * @IEEE80211_BCN_EMA_INDEX: generate beacon by periodicity index
> + *	if the value is >= this enum value.
> + */
> +enum ieee80211_bcn_tmpl_ema {
> +	IEEE80211_BCN_EMA_NONE	= -2,
> +	IEEE80211_BCN_EMA_NEXT	= -1,
> +	IEEE80211_BCN_EMA_INDEX	= 0,
> +};

I don't see this used in the new API below?

> +/** struct ieee80211_ema_bcn_list - list entry of an EMA beacon

missing newline

> + * Return: The nuber of entries in the list or 0 on error.
> + */
> +
> +int
> +ieee80211_beacon_get_template_ema_list(struct ieee80211_hw *hw,

could remove that newline and put the int on the same line, I guess?

> +				       struct ieee80211_vif *vif,
> +				       struct list_head *head);
> +
> +/**
> + * ieee80211_beacon_free_ema_list - free an EMA beacon template list
> + * @head: linked list head containing &struct ieee80211_ema_bcn_list pointers.
> + *
> + * This function will free a list previously acquired by calling
> + * ieee80211_beacon_get_template_ema_list()
> + */
> +
> +void
> +ieee80211_beacon_free_ema_list(struct list_head *head);

certainly here void fits on the line.

johannes


  reply	other threads:[~2020-11-06  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03  9:17 [PATCH V5 0/4] mac80211: add multiple bssid support John Crispin
2020-11-03  9:17 ` [PATCH V5 1/4] nl80211: add basic " John Crispin
2020-11-06  9:24   ` Johannes Berg
2020-11-06  9:26     ` Johannes Berg
2020-11-03  9:17 ` [PATCH V5 2/4] mac80211: add multiple bssid support to interface handling John Crispin
2020-11-03  9:17 ` [PATCH V5 3/4] mac80211: add multiple bssid/EMA support to beacon handling John Crispin
2020-11-06  9:31   ` Johannes Berg [this message]
2020-11-03  9:17 ` [PATCH V5 4/4] mac80211: don't allow CSA on non-transmitting interfaces John Crispin

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=020eb33ec1ed5cd5eb076eee7cc39a09a62bfdff.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=alokad@codeaurora.org \
    --cc=john@phrozen.org \
    --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