All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: senthilb@qti.qualcomm.com,
	SenthilKumar Jegadeesan <sjegadee@qti.qualcomm.com>,
	ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k:Prevent setting wrong key idx for station
Date: Thu, 29 Jan 2015 07:00:22 -0800	[thread overview]
Message-ID: <54CA4B06.10807@candelatech.com> (raw)
In-Reply-To: <87fvat3ml0.fsf@kamboji.qca.qualcomm.com>

I didn't realize it was only about WEP...probably not worth bothering
stable for just that.

Thanks,
Ben

On 01/29/2015 02:31 AM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> On 01/27/2015 06:30 AM, senthilb@qti.qualcomm.com wrote:
>>> From: SenthilKumar Jegadeesan <sjegadee@qti.qualcomm.com>
>>>
>>> Ath10k driver sets wrong default key idx that results in
>>> sending unicast frames with multicast key.
>>
>> Is this something that should be back-ported to stable releases?
>
> Sure, if somebody cares about WEP that much :)
>
> Should I add CC stable to the patch?
>

-- 
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

  parent reply	other threads:[~2015-01-29 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 14:30 [PATCH] ath10k:Prevent setting wrong key idx for station senthilb
2015-01-27 16:58 ` Ben Greear
2015-01-29 10:31   ` Kalle Valo
2015-01-29 12:31     ` SenthilKumar Jegadeesan
2015-01-29 15:00     ` Ben Greear [this message]
2015-01-28  8:23 ` Kalle Valo
2015-01-28  9:52   ` SenthilKumar Jegadeesan
2015-01-28 10:21     ` SenthilKumar Jegadeesan
2015-02-04  7:15 ` Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2015-01-27 14:21 Senthil Balasubramanian

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=54CA4B06.10807@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=senthilb@qti.qualcomm.com \
    --cc=sjegadee@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.