From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from sabertooth01.qualcomm.com ([65.197.215.72]) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1e6rBW-0006ru-KK for ath10k@lists.infradead.org; Tue, 24 Oct 2017 04:51:28 +0000 From: Kalle Valo Subject: Re: [PATCH] ath10k: rebuild crypto header in RX data frames Date: Tue, 24 Oct 2017 04:50:56 +0000 Message-ID: <8760b5cfnz.fsf@kamboji.qca.qualcomm.com> References: <150851690590.5158.11970481736247725763.stgit@potku.adurom.net> <87376dds5e.fsf@kamboji.qca.qualcomm.com> <9407ed1f-2bd9-3fd0-981d-1a20452e8ba9@dd-wrt.com> In-Reply-To: (Jasmine Strong's message of "Mon, 23 Oct 2017 11:28:18 -0700") Content-Language: en-US MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Jasmine Strong Cc: "linux-wireless@vger.kernel.org" , ath10k , Sebastian Gottschall Jasmine Strong writes: > That's what I saw. A bcom client was able to associate and not pass > any traffic. This is on all three of 9882, 9888 and 4019. Thanks for the report, we'll investigate it. And I see that your email was now succesfully delivered to the list: http://lists.infradead.org/pipermail/ath10k/2017-October/010325.html -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k