From: Sven Eckelmann <sven@narfation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH v3 2/3] mac80211: implement HE support for mesh
Date: Fri, 14 Jun 2019 16:13:32 +0200 [thread overview]
Message-ID: <2194147.kqlnQF7k4C@bentobox> (raw)
In-Reply-To: <8d0d11ca39b6216b24cf4e9e3a1522072db5c0d2.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Friday, 14 June 2019 16:11:15 CEST Johannes Berg wrote:
> > + ie_len = 2 + 1 +
> > + sizeof(he_cap->he_cap_elem) + n +
> > + ieee80211_he_ppe_size(he_cap->ppe_thres[0],
> > + he_cap->he_cap_elem.phy_cap_info);
> > +
> > + return ie_len;
>
> There's no value in the "ie_len" variable here.
Sorry, my parser just broke. Why is there no value in ie_len? Was just
assigned a line before. Or are you talking about something else?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-14 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 19:35 [PATCH v3 0/3] mac80211/ath11k: HE mesh support Sven Eckelmann
2019-06-12 19:35 ` [PATCH v3 1/3] mac80211_hwsim: Register support for HE meshpoint Sven Eckelmann
2019-06-12 19:35 ` [PATCH v3 2/3] mac80211: implement HE support for mesh Sven Eckelmann
2019-06-14 14:11 ` Johannes Berg
2019-06-14 14:13 ` Sven Eckelmann [this message]
2019-06-14 14:14 ` Johannes Berg
2019-06-12 19:35 ` [PATCH v3 3/3] ath11k: register HE mesh capabilities Sven Eckelmann
2019-06-14 14:10 ` [PATCH v3 0/3] mac80211/ath11k: HE mesh support Johannes Berg
2019-07-03 9:23 ` Sven Eckelmann
2019-07-12 7:58 ` Johannes Berg
2019-07-12 9:36 ` Sven Eckelmann
2019-07-12 9:42 ` Johannes Berg
2019-07-12 10:38 ` Sven Eckelmann
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=2194147.kqlnQF7k4C@bentobox \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.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).