From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jasmine Strong <jas@eero.com>
Cc: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
ath10k <ath10k@lists.infradead.org>,
Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath10k: rebuild crypto header in Rx data frames
Date: Wed, 25 Oct 2017 09:07:30 +0000 [thread overview]
Message-ID: <87d15boasv.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <CAGyitvNvCFAfuRg=uKLvZeZVzxsQ14GeXR702FHwu+RLLE_WAQ@mail.gmail.com> (Jasmine Strong's message of "Tue, 24 Oct 2017 14:15:22 -0700")
(fixing top posting)
Jasmine Strong <jas@eero.com> writes:
> On Tue, Oct 24, 2017 at 1:41 PM, Sebastian Gottschall
> <s.gottschall@dd-wrt.com> wrote:
>
>> patch works. tested in sta and ap mode so far on 9984
>
> Seems to work okay on mixed networks of 9882, 4019 and 9888.
Thanks Sebastian and Jasmine for testing this, very much appreciated. We
have a v3 coming up soon which should fix GCMP, GCMP-256 and CCMP-256 as
well.
--=20
Kalle Valo=
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jasmine Strong <jas@eero.com>
Cc: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: [PATCH v2] ath10k: rebuild crypto header in Rx data frames
Date: Wed, 25 Oct 2017 09:07:30 +0000 [thread overview]
Message-ID: <87d15boasv.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <CAGyitvNvCFAfuRg=uKLvZeZVzxsQ14GeXR702FHwu+RLLE_WAQ@mail.gmail.com> (Jasmine Strong's message of "Tue, 24 Oct 2017 14:15:22 -0700")
(fixing top posting)
Jasmine Strong <jas@eero.com> writes:
> On Tue, Oct 24, 2017 at 1:41 PM, Sebastian Gottschall
> <s.gottschall@dd-wrt.com> wrote:
>
>> patch works. tested in sta and ap mode so far on 9984
>
> Seems to work okay on mixed networks of 9882, 4019 and 9888.
Thanks Sebastian and Jasmine for testing this, very much appreciated. We
have a v3 coming up soon which should fix GCMP, GCMP-256 and CCMP-256 as
well.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-25 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 17:54 [PATCH v2] ath10k: rebuild crypto header in Rx data frames Kalle Valo
2017-10-24 17:54 ` Kalle Valo
2017-10-24 19:27 ` Sebastian Gottschall
2017-10-24 19:27 ` Sebastian Gottschall
2017-10-24 20:41 ` Sebastian Gottschall
2017-10-24 20:41 ` Sebastian Gottschall
2017-10-24 21:15 ` Jasmine Strong
2017-10-24 21:15 ` Jasmine Strong
2017-10-25 9:07 ` Kalle Valo [this message]
2017-10-25 9:07 ` Kalle Valo
2017-10-25 9:28 ` Sebastian Gottschall
2017-10-25 9:28 ` 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=87d15boasv.fsf@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=jas@eero.com \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
--cc=vthiagar@qti.qualcomm.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.