From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: Re: [v3] ath10k: rebuild crypto header in rx data frames
Date: Sat, 2 Dec 2017 13:41:07 -0800 [thread overview]
Message-ID: <73dae55c-4feb-b573-9d02-4942b201bec8@candelatech.com> (raw)
In-Reply-To: <878telw65j.fsf@kamboji.qca.qualcomm.com>
On 12/02/2017 06:34 AM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> Is this patch destined for stable?
>>
>> I was expecting to see it show up in the older stable releases,
>> but it has not so far as far as I can tell.
>
> We are working on it, but not sure yet to which releases, it doesn't
> directly apply to all active stable releases.
I had no luck trying to apply it to a 3.17-ish ath10k. Gave up after
a bit and tried backporting the whole stack instead :P
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-12-02 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 16:36 [PATCH v3] ath10k: rebuild crypto header in rx data frames Kalle Valo
2017-10-27 15:44 ` [v3] " Kalle Valo
2017-10-30 8:39 ` Kalle Valo
2017-10-30 9:32 ` Sebastian Gottschall
2017-10-31 14:52 ` Sebastian Gottschall
2017-10-31 15:00 ` Kalle Valo
2017-10-31 15:07 ` Sebastian Gottschall
2017-10-31 14:54 ` Sebastian Gottschall
2017-10-31 15:00 ` Vasanthakumar Thiagarajan
2017-11-21 18:54 ` Ben Greear
2017-12-02 14:34 ` Kalle Valo
2017-12-02 21:41 ` Ben Greear [this message]
2017-12-03 7:36 ` 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=73dae55c-4feb-b573-9d02-4942b201bec8@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox