From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 05/10] mac80211: handle HE 6 GHz Capability in HE STA processing
Date: Wed, 29 Apr 2020 17:11:24 -0700 [thread overview]
Message-ID: <a555a6cd27c5b100d2d11804c5b387de@codeaurora.org> (raw)
In-Reply-To: <8e55825d2c399dc926dacdc799fc64851d2fc4fb.camel@sipsolutions.net>
On 2020-04-29 07:31, Johannes Berg wrote:
> On Fri, 2020-04-24 at 15:41 -0700, Rajkumar Manoharan wrote:
>>
>> * @has_he: true iff HE data is valid.
>> + * @has_he_6ghz: true iff HE 6 GHz data is valid.
>> * @he_cap_elem: Fixed portion of the HE capabilities element.
>> * @he_mcs_nss_supp: The supported NSS/MCS combinations.
>> * @ppe_thres: Holds the PPE Thresholds data.
>> + * @ampdu_factor: Maximum A-MPDU length factor used in 6 GHz.
>> + * @ampdu_density: Minimum A-MPDU spacing used in 6 GHz.
>> + * @he_6gz_cap: HE 6 GHz Band capability.
>
> typo
>
>> */
>> struct ieee80211_sta_he_cap {
>> bool has_he;
>> + bool has_he_6ghz;
>> struct ieee80211_he_cap_elem he_cap_elem;
>> struct ieee80211_he_mcs_nss_supp he_mcs_nss_supp;
>> u8 ppe_thres[IEEE80211_HE_PPE_THRES_MAX_LEN];
>> + u8 ampdu_factor;
>> + u8 ampdu_density;
>> + u16 he_6ghz_cap;
>
> Maybe these should be in some kind of sub-struct so it's clear what the
> "has_he_6ghz" applies to?
>
Got it.
>> };
>>
>> /**
>> @@ -1272,7 +1280,7 @@ struct station_parameters {
>> u8 he_capa_len;
>> u16 airtime_weight;
>> struct sta_txpwr txpwr;
>> - const struct ieee80211_he_6ghz_band_cap *he_6ghz_capa;
>> + const u8 *he_6ghz_capa;
>
> hm?
>
I realized later ;) that ieee80211_he_cap_ie_to_sta_he_cap accepting u8*
for IEs.
To align with the existing pattern changed to u8 *. Let me correct it
first.
-Rajkumar
next prev parent reply other threads:[~2020-04-30 0:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 22:41 [PATCH 00/10] mac80211: add 6 GHz IEs support Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 01/10] mac80211: fix memory overlap due to variable length param Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 02/10] cfg80211: validate 6 GHz chandef Rajkumar Manoharan
2020-04-29 14:26 ` Johannes Berg
2020-04-30 0:02 ` Rajkumar Manoharan
2020-04-30 19:54 ` Johannes Berg
2020-04-24 22:41 ` [PATCH 03/10] nl80211: add HE 6 GHz Band Capability support Rajkumar Manoharan
2020-04-29 14:28 ` Johannes Berg
2020-04-30 0:04 ` Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 04/10] mac80211: add HE 6 GHz Band Capabilities into parse extension Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 05/10] mac80211: handle HE 6 GHz Capability in HE STA processing Rajkumar Manoharan
2020-04-29 14:31 ` Johannes Berg
2020-04-30 0:11 ` Rajkumar Manoharan [this message]
2020-04-24 22:41 ` [PATCH 06/10] mac80211: add HE 6 GHz Band Capability IE in assoc. request Rajkumar Manoharan
2020-04-29 14:33 ` Johannes Berg
2020-04-30 0:14 ` Rajkumar Manoharan
2020-04-30 19:52 ` Johannes Berg
2020-04-24 22:41 ` [PATCH 07/10] mac80211: build HE operation with 6 GHz oper information Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 08/10] mac80211: do not allow HT/VHT IEs in 6 GHz mesh mode Rajkumar Manoharan
2020-04-24 22:41 ` [PATCH 09/10] mac80211: determine chantype from HE operation in 6 GHz Rajkumar Manoharan
2020-04-29 14:34 ` Johannes Berg
2020-04-30 0:18 ` Rajkumar Manoharan
2020-04-30 19:53 ` Johannes Berg
2020-04-24 22:41 ` [PATCH 10/10] ath11k: build HE 6 GHz capability Rajkumar Manoharan
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=a555a6cd27c5b100d2d11804c5b387de@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).