ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: SenthilKumar Jegadeesan <sjegadee@qti.qualcomm.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: "Balasubramanian, Senthil Kumar" <senthilb@qti.qualcomm.com>,
	Ben Greear <greearb@candelatech.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k:Prevent setting wrong key idx for station
Date: Thu, 29 Jan 2015 18:01:47 +0530	[thread overview]
Message-ID: <20150129123145.GA11854@senthilj-ThinkPad-L430> (raw)
In-Reply-To: <87fvat3ml0.fsf@kamboji.qca.qualcomm.com>

On Thu, Jan 29, 2015 at 04:01:07PM +0530, Valo, Kalle 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?
> 
> -- 
> Kalle Valo

Considering the size of the patch  and WEP alg which is least used, I dont see
this change as  candidate for stable release backport.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2015-01-29 12:32 UTC|newest]

Thread overview: 9+ 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 [this message]
2015-01-29 15:00     ` Ben Greear
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

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=20150129123145.GA11854@senthilj-ThinkPad-L430 \
    --to=sjegadee@qti.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=senthilb@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