From: "Pedersen, Thomas" <twp@qca.qualcomm.com>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"openwrt-devel@lists.openwrt.org"
<openwrt-devel@lists.openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath10k mesh + ap + encryption?
Date: Fri, 23 Sep 2016 22:18:49 +0000 [thread overview]
Message-ID: <1474669037.16013.9.camel@qca.qualcomm.com> (raw)
In-Reply-To: <5898628.mmcCycDigQ@prime>
T24gTW9uLCAyMDE2LTA5LTE5IGF0IDA4OjQzICswMjAwLCBTaW1vbiBXdW5kZXJsaWNoIHdyb3Rl
Og0KPiBPbiBUdWVzZGF5LCBTZXB0ZW1iZXIgMTMsIDIwMTYgNTo1NDozOCBQTSBDRVNUIFBlZGVy
c2VuLCBUaG9tYXMgd3JvdGU6DQo+ID4gT24gVHVlLCAyMDE2LTA5LTEzIGF0IDE0OjMwICswMjAw
LCBTaW1vbiBXdW5kZXJsaWNoIHdyb3RlOg0KPiA+IA0KPiA+ID4gWy4uLl0NCj4gPiA+DQo+ID4g
PiBUaGFua3MgZm9yIHRoZSBjbGFyaWZpY2F0aW9uLiBXZSB3aWxsIHRoZW4gc3RpY2sgdG8gdGhl
IDcwJ3MgYnJhbmNoDQo+ID4gPiB0aGVuLg0KPiA+ID4gDQo+ID4gPiBEb2VzIGFueW9uZSBoYXZl
IHBvaW50ZXJzIGZvciB0aGUgb3RoZXIgcXVlc3Rpb25zPyA6KSBJIHdvdWxkIGJlbGlldmUNCj4g
PiA+IGhhdCBtYW55IA0KPiA+ID4gcGVvcGxlIHdvdWxkIGJlIGludGVyZXN0ZWQgaW4gcnVubmlu
ZyBBUCArIE1lc2ggZW5jcnlwdGVkIGF0IHRoZSBzYW1lDQo+ID4gPiB0aW1lIChhdCANCj4gPiA+
IGxlYXN0IGluIHRoZSBvcGVuIHNvdXJjZSBjb21tdW5pdHkgLi4uKS4NCj4gPiANCj4gPiANCj4g
PiBXZSdyZSB0ZXN0aW5nIGVuY3J5cHRlZCBBUCArIE1lc2ggcXVpdGUgc3VjY2Vzc2Z1bGx5IHJp
Z2h0IG5vdyB3aXRoDQo+ID4gdGhpcyBmaXJtd2FyZTogaHR0cHM6Ly9naXRodWIuY29tL2t2YWxv
L2F0aDEway1maXJtd2FyZS9jb21taXQvMzA3Y2I0NmINCj4gPiAwNjY2MWViZDMxODY3MjNiNTAw
MmRlNzY5YzdhZGQ4Mywgb2YgY291cnNlIHRoYXQgaXMgZm9yIGEgUUNBNDAxOSBjaGlwLg0KPiA+
IFdoaWNoIGNoaXAgYXJlIHlvdSB1c2luZz8gSSBjYW4gcG9rZSB0aGUgZmlybXdhcmUgZ3V5cyBm
b3IgcG9zc2liaWxpdHkNCj4gPiBvZiBnZXR0aW5nIGEgMTAuNC4zLjIgZmlybXdhcmUgYnVpbGQg
Zm9yIGl0Lg0KPiANCj4gSGkgVGhvbWFzLA0KPiANCj4gdGhhbmtzIGZvciB0aGUgaGludCEgV2Ug
YXJlIHVzaW5nIGFuIG9sZGVyIFFDQTk4ODIuIEkgYXNzdW1lIHlvdXIgZmlybXdhcmUgd2lsbCAN
Cj4gbm90IHdvcmsgZm9yIHRoaXMgb25lPyBJZiB5b3UgY2FuIHBva2UgdGhlIGZpcm13YXJlIGd1
eXMsIHRoYXQgd291bGQgYmUgZ3JlYXQuIA0KPiA6KQ0KDQpIaSBTaW1vbiwNCg0KQWNjb3JkaW5n
IHRvIGZpcm13YXJlIGd1eXMgdGhlIGxhdGVzdCBjb2RlIGNhbiBhY3R1YWxseSBjb21waWxlIGRv
d24gdG8NCmFueSBjaGlwc2V0LCBzbyBpdCBzaG91bGQgc2ltcGx5IGJlIGEgbWF0dGVyIG9mIGdl
dHRpbmcgYnVpbGRzIHJlbGVhc2VkLg0K
next prev parent reply other threads:[~2016-09-23 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:00 ath10k mesh + ap + encryption? Simon Wunderlich
2016-09-13 10:59 ` Valo, Kalle
2016-09-13 11:13 ` Simon Wunderlich
2016-09-13 11:25 ` Valo, Kalle
2016-09-13 11:38 ` Sebastian Gottschall
2016-09-13 12:30 ` Simon Wunderlich
2016-09-13 17:54 ` Pedersen, Thomas
2016-09-19 6:43 ` Simon Wunderlich
2016-09-19 9:34 ` [OpenWrt-Devel] " Sven Eckelmann
2017-01-24 16:41 ` Sven Eckelmann
2016-09-23 22:18 ` Pedersen, Thomas [this message]
2016-09-25 20:16 ` Simon Wunderlich
2016-09-13 18:54 ` Martin Blumenstingl
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=1474669037.16013.9.camel@qca.qualcomm.com \
--to=twp@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=openwrt-devel@lists.openwrt.org \
--cc=sw@simonwunderlich.de \
/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).