From: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: rebuild crypto header in RX data frames
Date: Mon, 23 Oct 2017 14:24:06 +0000 [thread overview]
Message-ID: <fb5f8df1-aa9a-2646-5f98-afc852acce5c@qti.qualcomm.com> (raw)
In-Reply-To: <c9bdd915-0667-eee0-3b52-1fdf15abf249@dd-wrt.com>
T24gU2F0dXJkYXkgMjEgT2N0b2JlciAyMDE3IDAxOjQxIEFNLCBTZWJhc3RpYW4gR290dHNjaGFs
bCB3cm90ZToNCj4gaSBzdWdnZXN0IHRoZSBmb2xsb3dpbmcgcGF0Y2ggb24gdG9wIG9mIHlvdXJz
LiBwbGVhc2UgdGVsbCBtZSBpZiBteSB0aG91Z2h0cyBhcmUgY29ycmVjdCBoZXJlLiBpdHMgbWFp
bmx5IGEgZ3Vlc3MNCg0KSSBhZ3JlZSB3ZSBuZWVkIHRvIHRha2UgY2FyZSBvZiB0aGlzIGZvciBu
ZXdseSBhZGRlZCBjaXBoZXJzIGFzIHdlbGwuIEhvdyBhYm91dCBtYWtpbmcgaXQgYXMgYSBzZXBh
cmF0ZSBwYXRjaCANCnRvIG1ha2UgdGhlIHBhdGNoIGJpdCBzbWFsbGVyIGFuZCB0byByZWR1Y2Ug
dGhlIGRpZmZpY3VsdGllcyBpbiBiYWNrIHBvcnRpbmcgaXQgZm9yIGNpcGhlcnMgc3VwcG9ydGVk
IGZvciBsb25nIA0KdGltZT8NCg0KVmFzYW50aA==
WARNING: multiple messages have this Message-ID (diff)
From: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: rebuild crypto header in RX data frames
Date: Mon, 23 Oct 2017 14:24:06 +0000 [thread overview]
Message-ID: <fb5f8df1-aa9a-2646-5f98-afc852acce5c@qti.qualcomm.com> (raw)
In-Reply-To: <c9bdd915-0667-eee0-3b52-1fdf15abf249@dd-wrt.com>
On Saturday 21 October 2017 01:41 AM, Sebastian Gottschall wrote:
> i suggest the following patch on top of yours. please tell me if my thoughts are correct here. its mainly a guess
I agree we need to take care of this for newly added ciphers as well. How about making it as a separate patch
to make the patch bit smaller and to reduce the difficulties in back porting it for ciphers supported for long
time?
Vasanth
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-23 14:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 16:28 [PATCH] ath10k: rebuild crypto header in RX data frames Kalle Valo
2017-10-20 16:28 ` Kalle Valo
2017-10-20 19:43 ` Sebastian Gottschall
2017-10-20 19:43 ` Sebastian Gottschall
2017-10-20 20:11 ` Sebastian Gottschall
2017-10-20 20:11 ` Sebastian Gottschall
[not found] ` <CAGyitvP0wquoo_8_ma3rcj+riJ5Wgfo7+pmbUOx9pQRwFcQHYA@mail.gmail.com>
2017-10-21 4:42 ` Kalle Valo
2017-10-21 4:42 ` Kalle Valo
2017-10-21 7:58 ` Sebastian Gottschall
2017-10-21 7:58 ` Sebastian Gottschall
2017-10-21 4:46 ` Kalle Valo
2017-10-22 10:26 ` Sebastian Gottschall
2017-10-22 10:31 ` Sebastian Gottschall
2017-10-23 18:28 ` Jasmine Strong
2017-10-24 4:50 ` Kalle Valo
2017-10-24 4:50 ` Kalle Valo
2017-10-24 16:09 ` Ben Greear
2017-10-24 16:09 ` Ben Greear
2017-10-24 19:19 ` Jasmine Strong
2017-10-24 19:19 ` Jasmine Strong
2017-10-23 14:24 ` Vasanthakumar Thiagarajan [this message]
2017-10-23 14:24 ` Vasanthakumar Thiagarajan
2017-10-23 19:35 ` Sebastian Gottschall
2017-10-23 19:35 ` Sebastian Gottschall
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=fb5f8df1-aa9a-2646-5f98-afc852acce5c@qti.qualcomm.com \
--to=vthiagar@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
/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.