From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Luca Coelho <luca@coelho.fi>, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
Liad Kaufman <liad.kaufman@intel.com>,
Johannes Berg <johannes.berg@intel.com>,
Ilan Peer <ilan.peer@intel.com>, Ido Yariv <idox.yariv@intel.com>
Subject: Re: [RFC 1/3] cfg80211: Add support for HE
Date: Mon, 28 May 2018 11:05:32 +0200 [thread overview]
Message-ID: <5B0BC65C.5010800@broadcom.com> (raw)
In-Reply-To: <37100d5380fcea97bfc83b92d4e1d89dbf52d674.camel@coelho.fi>
On 5/25/2018 9:51 PM, Luca Coelho wrote:
> Arend,
>
> On Fri, 2018-05-25 at 13:11 +0300, Luca Coelho wrote:
>> On Mon, 2018-05-21 at 21:47 +0200, Arend van Spriel wrote:
>>> On 5/18/2018 4:05 PM, Luca Coelho wrote:
>>>> @@ -781,6 +783,23 @@ int wiphy_register(struct wiphy *wiphy)
>>>> sband->channels[i].band = band;
>>>> }
>>>>
>>>> + for (i = 0; i < sband->n_iftype_data; i++) {
>>>> + const struct ieee80211_sband_iftype_data
>>>> *iftd;
>>>> +
>>>> + iftd = &sband->iftype_data[i];
>>>> +
>>>> + if (WARN_ON(!iftd->types))
>>>> + return -EINVAL;
>>>> + if (WARN_ON(types & iftd->types))
>>>> + return -EINVAL;
>>>
>>> I suspected the types mask was not allowed to overlap for the
>>> iftype_data entries, but may be worth documenting that in struct
>>> ieee80211_sband_iftype_data kerneldoc.
>>
>> Sure, I'll add it.
>
> Actually, looking into this again, I'm not sure I understand your
> comment. AFAICT this prevents the same type from appearing twice,
> right? I don't get the "not allowed to overlap"... Can you clarify?
I mean that iftdata entries can not overlap by having the same iftypes
set in their mask. So yes, a particular iftype may only be used in a
single entry (yet another way to say it ;-) ).
Gr. AvS
next prev parent reply other threads:[~2018-05-28 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 14:05 [RFC 0/3] cfg80211/mac80211: add support for IEEE802.11ax Luca Coelho
2018-05-18 14:05 ` [RFC 1/3] cfg80211: Add support for HE Luca Coelho
2018-05-21 19:47 ` Arend van Spriel
2018-05-25 10:11 ` Luca Coelho
2018-05-25 10:34 ` Arend van Spriel
2018-05-25 19:51 ` Luca Coelho
2018-05-28 9:05 ` Arend van Spriel [this message]
2018-05-18 14:05 ` [RFC 2/3] radiotap: add structs " Luca Coelho
2018-05-18 14:05 ` [RFC 3/3] mac80211: add support " Luca Coelho
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=5B0BC65C.5010800@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=idox.yariv@intel.com \
--cc=ilan.peer@intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=liad.kaufman@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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.