From: Johannes Berg <johannes@sipsolutions.net>
To: Sven Eckelmann <sven@narfation.org>, linux-wireless@vger.kernel.org
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH v3 0/3] mac80211/ath11k: HE mesh support
Date: Fri, 14 Jun 2019 16:10:46 +0200 [thread overview]
Message-ID: <c025150aad17bbe62595c4969ea2f53f009419d3.camel@sipsolutions.net> (raw)
In-Reply-To: <20190612193510.29489-1-sven@narfation.org> (sfid-20190612_213642_840659_91049B7E)
Hi Sven,
Two comments:
1) It seems to me that patches 1/2 really should be in opposite order,
since you can't really claim HE mesh support in hwsim when you don't
have it in mac80211?
Or maybe I misunderstand?
2) This series breaks the wpas_mesh_max_peering wpa_supplicant/hwsim
test, and I'm not sure why. Perhaps some length calculations are bad?
johannes
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-06-14 14:10 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
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 ` Johannes Berg [this message]
2019-07-03 9:23 ` [PATCH v3 0/3] mac80211/ath11k: HE mesh support 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=c025150aad17bbe62595c4969ea2f53f009419d3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sven@narfation.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